Re: PostgreSQL exception 0xC0000005
От | Guillaume Lelarge |
---|---|
Тема | Re: PostgreSQL exception 0xC0000005 |
Дата | |
Msg-id | 4C2237E3.1010901@lelarge.info обсуждение исходный текст |
Ответ на | PostgreSQL exception 0xC0000005 (Rawan AlSaad <rawan.alsaad@hotmail.com>) |
Список | pgadmin-support |
Le 23/06/2010 09:00, Rawan AlSaad a écrit : > [...] > I am having the following problem while using PostgreSQL 8.4 and PostGIS > 1.5 when I run the following query: > > SELECT * FROM shortest_path('SELECT id::int4, source::int4, > > target::int4, cost from edges2',257180448,651912268, true, false); > > The PostgreSQL server connection terminates and I am unable to reconnect > to it until I restart my PC. > > The log file shows the following: > > 2010-06-22 21:13:48 ASTLOG: server process (PID 764) was terminated by > *exception 0xC0000005* > > 2010-06-22 21:13:48 ASTHINT: See C include file "ntstatus.h" for a > description of the hexadecimal value. > > 2010-06-22 21:13:48 ASTLOG: terminating any other active server processes > > 2010-06-22 21:13:48 ASTWARNING: terminating connection because of crash > of another server process > > 2010-06-22 21:13:48 ASTDETAIL: 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. > > 2010-06-22 21:13:48 ASTHINT: In a moment you should be able to > reconnect to the database and repeat your command. > > 2010-06-22 21:13:48 ASTWARNING: terminating connection because of crash > of another server process > > 2010-06-22 21:13:48 ASTDETAIL: 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. > > 2010-06-22 21:13:48 ASTHINT: In a moment you should be able to > reconnect to the database and repeat your command. > > 2010-06-22 21:13:48 ASTLOG: all server processes terminated; reinitializing > > 2010-06-22 21:13:58 ASTFATAL: pre-existing shared memory block is still > in use > > 2010-06-22 21:13:58 ASTHINT: Check if there are any old server > processes still running, and terminate them. > > Could anybody please help explaining for me what might be the cause for > this exception and how can I fix the problem??? > You should better ask on a PostGIS mailing list. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com
В списке pgadmin-support по дате отправления: