Re: pqReadData() - backend unexpectedly closed the channel
От | Frank Miles |
---|---|
Тема | Re: pqReadData() - backend unexpectedly closed the channel |
Дата | |
Msg-id | Pine.A41.4.33.0103130750400.7762-100000@mead4.u.washington.edu обсуждение исходный текст |
Ответ на | pqReadData() - backend unexpectedly closed the channel ("Scott Price" <Scott.Price@sci.com>) |
Список | 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 repeatedlygetting "pqReadData - backend closed the channel unexpectedly. This probably means that .... the backend abruptlyterminated before or while your request was being processed" (or something close to those words). The last responseI saw from postgresql.org to Frank was from a fellow Tom Lane asking to see a core dump. Since I experienced thisproblem I would like to send you a core dump of my file (which is gzipped), core.gz, and if you all could give me anyexplanations 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.price@sci.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
В списке pgsql-general по дате отправления: