> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 13, 2006 11:12 AM
>
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > On Thu, Jul 13, 2006 at 08:22:46AM -0500, Medora Schauer wrote:
> >> Can it be that the connection delay is because first an IPv6 socket
is
> >> trying to be establi
Michael Fuhr <[EMAIL PROTECTED]> writes:
> On Thu, Jul 13, 2006 at 08:22:46AM -0500, Medora Schauer wrote:
>> Can it be that the connection delay is because first an IPv6 socket is
>> trying to be established and when that fails an IPv4 socket is created?
> A sniffer like tcpdump or ethereal might
On Thu, Jul 13, 2006 at 08:22:46AM -0500, Medora Schauer wrote:
> Can it be that the connection delay is because first an IPv6 socket is
> trying to be established and when that fails an IPv4 socket is created?
A sniffer like tcpdump or ethereal might reveal why connecting is
so slow. The problem
> From: Bruno Wolff III [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 12, 2006 8:54 PM
> To: Medora Schauer
> Cc: postgresql
> Subject: Re: hyper slow after upgrade to 8.1.4
>
> On Wed, Jul 12, 2006 at 15:41:14 -0500,
> Medora Schauer <[EMAIL PROTECTED]> wrote:
> > I have just upgraded from
On Wed, Jul 12, 2006 at 15:41:14 -0500,
Medora Schauer <[EMAIL PROTECTED]> wrote:
> I have just upgraded from 7.3.4 to 8.1.4 and now *all* db access calls
> are extremely slow. I didn't need to preserve any old data so at this
> point all my tables are empty. Just connecting to a db takes sever
On Wednesday 12 July 2006 13:41, Medora Schauer wrote:
> I have just upgraded from 7.3.4 to 8.1.4 and now *all* db access calls
> are extremely slow. I didn't need to preserve any old data so at this
> point all my tables are empty. Just connecting to a db takes several
> seconds.
>
>
>
> When I
