Re: Re: [GENERAL] libpq error codes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Denis Perchine <dyp(at)perchine(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Re: [GENERAL] libpq error codes
Date: 2000-06-22 15:17:35
Message-ID: 8755.961687055@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

Denis Perchine <dyp(at)perchine(dot)com> writes:
> db=> select count(*) from pg_class;
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> !>

> Looks much more reasonable. But I do not get messages about shutdown.
> With a patch enclosed it will perform like with ECONNRESET.
> Shouldn't I emulate EOF when EPIPE?

You *are* emulating EOF --- with that check in place, pqReadData
should respond to EPIPE just like it does to a normal EOF. I don't
understand why you aren't seeing the same results I do.

How exactly are you testing this? I'm doing it with a plain "kill"
on the connected backend process. If you were using "kill -9"
or some such, that'd explain it --- the backend doesn't have an
opportunity to send the "I'm shutting down" message in that case.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Denis Perchine 2000-06-22 15:40:40 Re: Re: [GENERAL] libpq error codes
Previous Message Robert D. Nelson 2000-06-22 12:05:00 RE: Postgres with php3

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2000-06-22 15:27:30 Re: Big 7.1 open items
Previous Message Bruce Momjian 2000-06-22 14:35:19 Re: Big 7.1 open items