From: Sharmad Naik <sharmad@goatelecom.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: error in postgresql
Date: Sun, 11 Nov 2001 21:13:15 +0530
Message-ID: <20011111211315.A630@goatelecom.com> (raw)
In-Reply-To: <2628.1004478416@sss.pgh.pa.us>
References: <3bde7ee4.753.0@punweb01>
<2628.1004478416@sss.pgh.pa.us>
Hi,
Firstly I'm Sorry for the delay in replying.
When I gave a search for core file I didn't seems to
exist.pg_dump didnot create the core file
well if i tried to even query the table of the database it
would directly close the connection with the backend giving the
prompt like #> and displaying a similar message shown below.
Pls direct me.
-TIA
Sharmad
Pls cc a copy to sharmad@softhome.net
On Tue, Oct 30, 2001 at 04:46:56PM -0500, Tom Lane wrote:
> 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.
--
Feel free to contact me (flames about my english and the useless of this
driver will be redirected to /dev/null, oh no, it's full...).
(Michael Beck, describing the PC-speaker sound device)
---------------------
__ _ _ _ _
|_|_||_||_||\/||_|| \
_|| || || \| || ||_/
"What we cannot speak about we must pass over in silence."
Ludwig Wittgenstein (1889-1951), Austrian philosopher
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: sharmad@goatelecom.com, tgl@sss.pgh.pa.us
Subject: Re: error in postgresql
In-Reply-To: <20011111211315.A630@goatelecom.com>
* 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