From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Haron, Charles" <charles(dot)haron(at)cognitive(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org, Richard Poole <rp(at)guests(dot)deus(dot)net> |
Subject: | Re: Trouble Escaping Quotes |
Date: | 2005-01-24 19:13:41 |
Message-ID: | 23826.1106594021@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Haron, Charles" <charles(dot)haron(at)cognitive(dot)com> writes:
> *** Information From <posgresqlhome>/data/serverlog ***
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: WARNING:
> Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend
> died abnormally and possibly corrupted shared memory.
Hmm. That moves it out of the realm of "user error", which is what
I think we'd all been assuming, and into the realm of "server bug".
Can you supply a self-contained test case that causes this? Or at
least a debugger back trace from the point of the core dump?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jani Averbach | 2005-01-24 19:15:15 | Re: pg_dump --data-only problem with PgSQL 8.0 |
Previous Message | Tom Lane | 2005-01-24 18:46:38 | Re: pg_dump --data-only problem with PgSQL 8.0 |