Re: FE/BE protocol oddity - Mailing list pgsql-hackers

From Tom Lane
Subject Re: FE/BE protocol oddity
Date
Msg-id 17688.994444416@sss.pgh.pa.us
Whole thread Raw
In response to Re: FE/BE protocol oddity  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: FE/BE protocol oddity
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I guess there is sort of a point there.  So I'm leaning towards adding a
> "startup complete" flag somewhere in PGconn and simply fix up
> closePGconn().

I think you can use the conn->status field; you shouldn't need a new
flag, just test whether status is CONNECTION_OK or not.

> Seriously, in the worst case we'll get EINVAL.

So you'll just ignore an error?  Okay, that'll probably work.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Rule action ordering
Next
From: Gunnar Rønning
Date:
Subject: Re: Database Users Management and Privileges