| From: | "Scott Price" <Scott(dot)Price(at)sci(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org>, "<Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | pqReadData() - backend unexpectedly closed the channel |
| Date: | 2001-03-13 00:56:30 |
| Message-ID: | saad1be8.006@gwise2.sci.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
Thanks,
Scott M. Price
| Attachment | Content-Type | Size |
|---|---|---|
| core.gz | application/x-gzip | 200.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tc lewis | 2001-03-13 01:26:51 | socket file must reside in /tmp? |
| Previous Message | Jeff Schnitzer | 2001-03-13 00:45:44 | Case insensitive primary keys |