Re: PQsetdbLogin bug? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PQsetdbLogin bug?
Date
Msg-id 5041.990800771@sss.pgh.pa.us
Whole thread Raw
In response to PQsetdbLogin bug?  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: PQsetdbLogin bug?  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> 2) check if the status of handle returned PQsetdbLogin is
>    CONNECTION_BAD closePGconn. if so, do not call pqPuts (and
>    pqFlush)

I like this approach.  The other way, you'd have to be sure that all
failure paths close the socket before returning; even if you get it
right today, somebody will break it again in future.  The sending of
the final 'X' is really quite optional anyhow, so I'd say it's fine
not to do it when there's any question about whether it's safe.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug#98643: plpgsql SELECT INTO causes trouble when assignment impossible (fwd)
Next
From: Teodor Sigaev
Date:
Subject: Re: GiST index on data types that require compression