Received: from sss.pgh.pa.us (sss-backup.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9ULlmP52779 for ; Tue, 30 Oct 2001 16:47:48 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9ULkvc02631; Tue, 30 Oct 2001 16:46:57 -0500 (EST) To: sharmad@goatelecom.com cc: pgsql-sql@postgresql.org Subject: Re: error in postgresql In-reply-to: <3bde7ee4.753.0@punweb01> References: <3bde7ee4.753.0@punweb01> Comments: In-reply-to sharmad@goatelecom.com message dated "Tue, 30 Oct 2001 15:50:20 +0550" Date: Tue, 30 Oct 2001 16:46:56 -0500 Message-ID: <2628.1004478416@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/423 X-Sequence-Number: 5374 sharmad@goatelecom.com writes: > postgres@linux:~ > pg_dumpall > alllms_30-10-2001.bak > SQL query to dump the contents of Table 'common_to_three' did not execute. Explanation from backend: 'pqReadData() -- backend closed the channel unexpectedly. > This probably means the backend terminated abnormally > before or while processing the request. > '. > The query was: 'COPY "common_to_three" TO stdout; Hm. The only cases I can recall of backend crashes during COPY OUT were caused by corrupted data. Do you get similar failures if you do "SELECT * FROM common_to_three"? You could investigate more closely by using gdb to look at the core file left by the crashed backend. A backtrace would give us at least some idea of the nature of the problem. regards, tom lane