pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
error in postgresql
5+ messages / 3 participants
[nested] [flat]

* error in postgresql
@ 2001-10-30 10:00  sharmad@goatelecom.com
  0 siblings, 1 reply; 5+ messages in thread

From: sharmad@goatelecom.com @ 2001-10-30 10:00 UTC (permalink / raw)
  To: pgsql-sql; +Cc: g@punweb01

pls check for the error and tell me if any solution can be come upon. 
TIA
Sharmad

Attachments:

errorinpostgres (text/plain, 502B) download Script started on Tue Oct 30 10:24:36 2001 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; '. pg_dump failed on lms, exiting postgres@linux:~ > Script done on Tue Oct 30 10:24:48 2001
^ permalink raw reply [nested|flat] 5+ messages in thread

* Re: error in postgresql
@ 2001-10-30 21:46  Tom Lane <tgl@sss.pgh.pa.us>
  parent: sharmad@goatelecom.com
  0 siblings, 1 reply; 5+ messages in thread

From: Tom Lane @ 2001-10-30 21:46 UTC (permalink / raw)
  To: sharmad@goatelecom.com; +Cc: pgsql-sql

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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: error in postgresql
@ 2001-11-11 15:43  Sharmad Naik <sharmad@goatelecom.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 5+ messages in thread

From: Sharmad Naik @ 2001-11-11 15:43 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-sql

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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: error in postgresql
@ 2001-11-11 17:00  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Sharmad Naik <sharmad@goatelecom.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Tom Lane @ 2001-11-11 17:00 UTC (permalink / raw)
  To: Sharmad Naik <sharmad@goatelecom.com>; +Cc: pgsql-sql

Sharmad Naik <sharmad@goatelecom.com> writes:
> 	When I gave a search for core file I didn't seems to
> exist.pg_dump didnot create the core file

pg_dump isn't coring, it's the backend.  Backend core files normally
appear in $PGDATA/base/whicheverdb/.  If you don't see one there,
it's likely because you started the postmaster under "ulimit -c 0"
(this seems to be the default for init-script-started processes on
at least some Linux distros :-().  Restart it with "ulimit -c unlimited"
and try again.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: error in postgresql
@ 2001-11-15 06:56  Sharmad Naik <sharmad@goatelecom.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 5+ messages in thread

From: Sharmad Naik @ 2001-11-15 06:56 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-sql

Hi Tom,
	It's not there. Now do i say 
	postmaster -D <directory name of dbase> ulimit -c 0
Is this right?
-TIA
Sharmad

On Sun, Nov 11, 2001 at 12:00:39PM -0500, Tom Lane wrote:
> Sharmad Naik <sharmad@goatelecom.com> writes:
> > 	When I gave a search for core file I didn't seems to
> > exist.pg_dump didnot create the core file
> 
> pg_dump isn't coring, it's the backend.  Backend core files normally
> appear in $PGDATA/base/whicheverdb/.  If you don't see one there,
> it's likely because you started the postmaster under "ulimit -c 0"
> (this seems to be the default for init-script-started processes on
> at least some Linux distros :-().  Restart it with "ulimit -c unlimited"
> and try again.
> 
> 			regards, tom lane

-- 
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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2001-11-15 06:56 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-10-30 10:00 error in postgresql sharmad@goatelecom.com
2001-10-30 21:46 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-11-11 15:43   ` Sharmad Naik <sharmad@goatelecom.com>
2001-11-11 17:00     ` Tom Lane <tgl@sss.pgh.pa.us>
2001-11-15 06:56       ` Sharmad Naik <sharmad@goatelecom.com>

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