From: Tom Lane <tgl@sss.pgh.pa.us>
To: sharmad@goatelecom.com
Cc: pgsql-sql@postgresql.org
Subject: Re: error in postgresql
Date: Tue, 30 Oct 2001 16:46:56 -0500
Message-ID: <2628.1004478416@sss.pgh.pa.us> (raw)
In-Reply-To: <3bde7ee4.753.0@punweb01>
References: <3bde7ee4.753.0@punweb01>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, sharmad@goatelecom.com
Subject: Re: error in postgresql
In-Reply-To: <2628.1004478416@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox