Re: libpq and TOO MANY CONNECTIONS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: libpq and TOO MANY CONNECTIONS
Date
Msg-id 2449.1281636834@sss.pgh.pa.us
Whole thread Raw
In response to libpq and TOO MANY CONNECTIONS  (Dmitriy Igrishin <dmitigr@gmail.com>)
List pgsql-hackers
Dmitriy Igrishin <dmitigr@gmail.com> writes:
> It seams, that all of the error codes should be obtained by calling
> PQresultErrorField().
> But this function works only with results. So in what situations
> TOO MANY CONNECTIONS error may be thrown after successfully connection ? :)

It isn't.

The lack of a way to report a SQLSTATE code for a connection failure is
an API shortcoming in libpq; it's not the backend's problem.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: including backend ID in relpath of temp rels - updated patch
Next
From: Tom Lane
Date:
Subject: Re: CommitFest 2010-07 week four progress report