Re: Reposnse from backend when wrong user/database request send - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Reposnse from backend when wrong user/database request send
Date
Msg-id 16802.1268432695@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reposnse from backend when wrong user/database request send  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: Reposnse from backend when wrong user/database request send
List pgsql-hackers
Tatsuo Ishii <ishii@postgresql.org> writes:
>> Tatsuo Ishii <ishii@postgresql.org> writes:
>>> It seems between 8.4 and CVS HEAD backend responses 'E' packet
>>> (error/fatal message) if a startup packet sent with wrong user and/or
>>> database. Before backend responses 'R' packet first followd by 'E'
>>> packet.

> I now understand that those behavior could be changed randomly release
> to relase in unpredictable way.

I think the protocol specification is pretty explicit that you shouldn't
be relying on specific sequences of events where it's not logically
necessary that things happen in a particular order.  It's always been
possible for a connection to be rejected before any 'R' is sent; we've
only made a minor change in the set of error cases for which that's
true.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: buildfarm logging versus embedded nulls
Next
From: Robert Haas
Date:
Subject: Re: Dyamic updates of NEW with pl/pgsql