Re: [PATCHES] default database creation with initdb

Tom Lane wrote:
> Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
>
>>Fallback is a fine idea, but this brings up another problem I'm
>>currently facing: how to identify the problem the connection has from
>>libpq? If the problem is a wrong password, we certainly don't want to
>>try again. I browsed the sources over and over, but apparently there's
>>no machine readable return code to distinguish the reason of connection
>>failure apart from examining the errormessage string.
>
>
> If it's a server-side failure it should have a SQLSTATE code. I think
> it'd be OK to look for ERRCODE_UNDEFINED_DATABASE to determine this.

SQLSTATE?
Specifically, I'm talking about

"no pg_hba.conf entry for ....", "Ident authentication failed.." (both
server sice) and "Is the server running on host ..." from libpq which I
receive from PQerrorMessage after PQconnectdb; I only receive
CONNECTION_BAD from PQstatus where I'd like it a little more specific
(maybe an PQextendedStatus)

Regards,
Andreas