Ticket #149 (new bug report)
terminate called after throwing an instance of 'std::length_error' what(): vector::_M_fill_insert
Reported by: | olivermay | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | Version 1.1 |
Component: | Dijkstra | Version: | 1.03 |
Keywords: | crash, error | Cc: |
Description
calculating a route using the command: SELECT * FROM shortest_path('SELECT gid as id, ref_in_id::integer as source, nref_in_id::integer as target, length as cost, x1, y1, x2, y2 FROM street_lam72_test2', 545078377, 539375234, false, false); results in postgres crashing, the command just returns ********** Error ********** (in pgAdmin3). The postgres logfiles says: terminate called after throwing an instance of 'std::length_error'
what(): vector::_M_fill_insert
2009-03-05 15:48:54 CET LOG: server process (PID 11230) was terminated by signal 6: Aborted 2009-03-05 15:48:54 CET LOG: terminating any other active server processes 2009-03-05 15:48:54 CET WARNING: terminating connection because of crash of another server process 2009-03-05 15:48:54 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2009-03-05 15:48:54 CET HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-03-05 15:48:54 CET WARNING: terminating connection because of crash of another server process 2009-03-05 15:48:54 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2009-03-05 15:48:54 CET HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-03-05 15:48:54 CET LOG: all server processes terminated; reinitializing 2009-03-05 15:48:54 CET LOG: database system was interrupted; last known up at 2009-03-05 15:48:25 CET 2009-03-05 15:48:54 CET LOG: database system was not properly shut down; automatic recovery in progress 2009-03-05 15:48:54 CET LOG: unexpected pageaddr 0/224A6000 in log file 0, segment 41, offset 4874240 2009-03-05 15:48:54 CET LOG: redo is not required 2009-03-05 15:48:54 CET LOG: autovacuum launcher started 2009-03-05 15:48:54 CET LOG: database system is ready to accept connections
I can't figure out if this problem originates in our dataset or if there went something wrong compiling... Versions:
OS: ubuntu 8.10 Kernel: Linux pretoria 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux Postgres: 8.3.4-2.2 Libboost: 1.35.0-8ubuntu1
I compiled with neither the DD or TSP algorithms.
I already tried other versions: Trunk, 1.02 & 1.03 result in the same error.