Re: backend closed the channel unexpectedly?!?
От | Sean Kelly |
---|---|
Тема | Re: backend closed the channel unexpectedly?!? |
Дата | |
Msg-id | 20001109161413.021FE556F@random.ncl.ac.uk обсуждение исходный текст |
Ответ на | backend closed the channel unexpectedly?!? (Martti Hertzen <hertzma@sqc.fi>) |
Список | pgsql-bugs |
On Wed, 08 Nov 2000 16:54:40 +0200, Martti Hertzen said: > testsqc=> DELETE FROM henkilo WHERE id = 12; > pqReadData() -- backend closed the channel unexpectedly. > This probably means the backend terminated abnormally > before or while processing the request. > The connection to the server was lost. Attempting reset: Failed. > !> > > Here's the output of the debug channel: > > 001108.16:31:16.753 [31195] StartTransactionCommand > 001108.16:31:16.753 [31195] query: DELETE FROM henkilo WHERE id = 12; > 001108.16:31:16.840 [31195] ProcessQuery > postmaster: reaping dead processes... > postmaster: CleanupProc: pid 31195 exited with status 139 > Server process (pid 31195) exited with status 139 at Wed Nov 8 16:31:17 > 2000 > Terminating any active server processes... > Server processes were terminated at Wed Nov 8 16:31:17 2000 > Reinitializing shared memory and semaphores > 001108.16:31:17.822 [30871] shmem_exit(0) > binding ShmemCreate(key=52e4b5, size=1104896) I had this problem after renaming OLD_TABLE to NEW_TABLE after creating foreign keys in OLD_TABLE referencing MASTER_TABLE. Listen to Tom ... he knows his stuff ;) -- Sean Kelly <S.Kelly@ncl.ac.uk> "If 99% is good enough, then gravity will not work for 14 minutes every day."
В списке pgsql-bugs по дате отправления: