Re: [HACKERS] Re: SIGPIPE gripe - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Re: SIGPIPE gripe
Date
Msg-id 14199.894316596@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: SIGPIPE gripe  (dg@illustra.com (David Gould))
List pgsql-hackers
dg@illustra.com (David Gould) writes:
>> So ... since we're altering the protocol anyway ... the right fix is
>> to alter the protocol a little more.
>>
>> Client waits for "Z" ; if get "E" instead, BE startup failed.

> BE fails, client gets SIGPIPE? or client waits forever?

Neither: the client detects EOF on its input and realizes that the
backend failed.  Already done and tested.

(SIGPIPE is only for *write* on a closed channel, not *read*.
Read just returns EOF.)

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Postgresql6.3.2 libdld and the twilight zone.
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] RE: [QUESTIONS] Best way to halt an unending query.