From: | Sean Kelly <S(dot)Kelly(at)ncl(dot)ac(dot)uk> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Cc: | hertzma(at)sqc(dot)fi |
Subject: | Re: backend closed the channel unexpectedly?!? |
Date: | 2000-11-09 16:14:09 |
Message-ID: | 20001109161413.021FE556F@random.ncl.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)Kelly(at)ncl(dot)ac(dot)uk>
"If 99% is good enough, then gravity will not work for 14 minutes
every day."
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Miles | 2000-11-10 05:52:30 | index(fct(primary key)) kills INSERTs |
Previous Message | Karel Zak | 2000-11-09 07:41:30 | Re: Re: to_date problems (Re: Favor for Postgres User at WSI) |