From: | Neil <neil(at)hica(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: message type 0x44 |
Date: | 2004-12-07 05:39:37 |
Message-ID: | 6.1.1.1.2.20041207163032.025306a8@mail.hica.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Sys logging is not enabled :(, I am just looking for another way. There is
some logging going to stdout, nothing however with this problem. I think
there is a way of sending this log info to a file, just have to workout
where :)
At 04:13 PM 7/12/2004, Tom Lane wrote:
>Neil <neil(at)hica(dot)com(dot)au> writes:
> > $ pg_dump: message type 0x44 arrived from server while idle
> > $ pg_dump: dumpClasses(): SQL command failed
> > $pg_dump: Error message from server: server closed the connection
> unexpectedly
> > This probably means the server terminated abnormally
> > before or while processing the request.
> > $ pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor
>
>This is definitely Not Good. What shows up in the postmaster log when
>this happens?
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-12-07 06:01:09 | Re: message type 0x44 |
Previous Message | Michael Fuhr | 2004-12-07 05:21:07 | Re: triggers, transactions and locks |