From: | Frank Miles <fpm(at)u(dot)washington(dot)edu> |
---|---|
To: | Scott Price <Scott(dot)Price(at)sci(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org>, "<Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: pqReadData() - backend unexpectedly closed the channel |
Date: | 2001-03-13 15:55:00 |
Message-ID: | Pine.A41.4.33.0103130750400.7762-100000@mead4.u.washington.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 12 Mar 2001, Scott Price wrote:
> To: Tom Lane, and Postgresql.org staff,
>
> This is a message in response to the one sent by Frank Miles on Tue 7 Nov 2000 11:11:29 -0800 (PST).
>
> I have been experiencing the same problem as the gentleman, Frank Miles, when running Postgre SQL. I have been repeatedly getting "pqReadData - backend closed the channel unexpectedly. This probably means that .... the backend abruptly terminated before or while your request was being processed" (or something close to those words). The last response I saw from postgresql.org to Frank was from a fellow Tom Lane asking to see a core dump. Since I experienced this problem I would like to send you a core dump of my file (which is gzipped), core.gz, and if you all could give me any explanations or recommendations, I'd appreciate it.
>
> Postgre SQL Version 6.5.3 on i686-pc-linux-gnu, compiled by gcc egcs-2.91.66.
>
> My email: scott(dot)price(at)sci(dot)com
My dim recollection was that the underlying problem was that a table had been renamed
(bad order of operations!!), damaging one or more foreign key links. I was able to
fix it by editing a pg_dump'ed version of the database, and restoring the database
from the dump, thereby repairing the FK links.
Your problem may be different!
-frank
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-13 16:02:01 | Re: Trigger Compile Error |
Previous Message | Jean-Christophe Boggio | 2001-03-13 15:54:00 | Where's that doc on plans ? |