Re: Reposnse from backend when wrong user/database request send

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reposnse from backend when wrong user/database request send
Date: 2010-03-12 22:01:55
Message-ID: 20100313.070155.81686247.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.
>
> > Does anybody know why this change made?
>
> It's a side effect of the changes made to get rid of the flat
> authorization files. Bad database is now reported before authentication
> instead of after. I wouldn't have thought bad user per se would be
> reported before auth, though --- you sure about that one?

No. Just a logical conjecture.

So the change was made not to fix the bug(IMO).

I now understand that those behavior could be changed randomly release
to relase in unpredictable way.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-03-12 22:11:48 Re: buildfarm logging versus embedded nulls
Previous Message Alvaro Herrera 2010-03-12 21:45:28 Re: buildfarm logging versus embedded nulls