On Wed, 26 Feb 2003, Tom Lane wrote:
> Are you sure you turned off SSL? (I am not sure it's possible to do that
> just by altering pg_hba.conf --- you can force SSL that way, but not
> forbid it.)
Ah, my mistake. I was wrong in thinking going from hostssl to host
in pg_hba.conf would force non-S
Randy Cone <[EMAIL PROTECTED]> writes:
> What's particularly irksome is that this happens even when no SSL is
> supposed to be used at all, i.e. simple tcp/ip host based client connect.
Hard to see how that could happen, unless some SSL logic has snuck into
the non-SSL code path --- but then I'd e
On Wed, 26 Feb 2003, Tom Lane wrote:
> Randy Cone <[EMAIL PROTECTED]> writes:
> > I'm getting this on large inserts when connecting via perl's DBD::Pg using
[...]
> You sure you are on 7.3.2 --- at both ends? This looks like the problem
> allegedly fixed by this patch:
>
[...]
> Nathan
Randy Cone <[EMAIL PROTECTED]> writes:
> I'm getting this on large inserts when connecting via perl's DBD::Pg using
> on *both* hostssl and host access methods:
> Feb 26 10:57:23 scylla postgres[25273]: [1] LOG: connection received:
> host=127.0.0.1 port=35399
> Feb 26 10:57:23 scylla postgres[25
Folks,
I'm getting this on large inserts when connecting via perl's DBD::Pg using
on *both* hostssl and host access methods:
Feb 26 10:57:23 scylla postgres[25273]: [1] LOG: connection received:
host=127.0.0.1 port=35399
Feb 26 10:57:23 scylla postgres[25273]: [2] LOG: connection authorized:
us
