| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Reposnse from backend when wrong user/database request send |
| Date: | 2010-03-12 22:24:55 |
| Message-ID: | 16802.1268432695@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
>> Tatsuo Ishii <ishii(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-03-12 22:41:18 | Re: Dyamic updates of NEW with pl/pgsql |
| Previous Message | Tom Lane | 2010-03-12 22:11:48 | Re: buildfarm logging versus embedded nulls |