Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Is this a TODO? I don't see how it is a new problem, meaning it
> > probably is for 8.3.
>
> It's definitely not a new problem, but we hadn't recognized it before,
> so it qualifies as a new bug. The question at hand was whether any
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Is this a TODO? I don't see how it is a new problem, meaning it
> probably is for 8.3.
It's definitely not a new problem, but we hadn't recognized it before,
so it qualifies as a new bug. The question at hand was whether anyone
was excited enough about
Is this a TODO? I don't see how it is a new problem, meaning it
probably is for 8.3.
---
Tom Lane wrote:
> As per a recent discussion in pgsql-admin,
> http://archives.postgresql.org/pgsql-admin/2006-09/msg00297.php
> libpq
On Tue, Sep 26, 2006 at 02:18:59PM -0400, Tom Lane wrote:
> at the error string is of course not localization-proof, so we'd have to
> break down that errcode into some more-specific categories. Which is
> probably not a bad idea anyway, but it would mean that the nicer
> behavior would only happe
As per a recent discussion in pgsql-admin,
http://archives.postgresql.org/pgsql-admin/2006-09/msg00297.php
libpq doesn't cope well with the situation where the server is
configured to allow only SSL connections (or only non-SSL connections)
and there is some unrelated-to-SSL connection problem such
