Re: BUG #5246: Misleading/inconsistent SQLSTATE behavior

"Chris Travers" <chris.travers@gmail.com> wrote:

> I am noticing that that a failed database connection results in an
> unusable SQLSTATE in libpq, and a very different SQLSTATE than the
> backend registers.

Well, if the client fails to connect to the server, I'm not sure how
the server could communicate its SQLSTATE to the client, in order to
force them to match.

> For example, if a connection fails due to a database not found,
> ... the front-end registers 25P01.

I would have expected something in the 08 class, like maybe 08001 or
08004.

> login fails,  ... the front-end registers 25P01 again.

That definitely sounds like it should use 08001.

-Kevin