Andrus, Is correct. There is no DNS involved because I am using 127.0.0.1 in
my config
and when connecting. But there is still a ~60second delay connecting and
more delays
to return the select * query.
I have other servers using 127.0.0.1 like Apache,MySql and none have this
delay connecting and working so I am sure it is Postmaster related.
Any suggestions on different configurations that I can try, pgSql is
unusable to me
if I cannot solve this issue and I need it pretty quick now.
TIA
Scott
From: "Andrus" <eetasoft@xxxxxxxxx>
To: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: (Win32 Postgres) Slow to Connect first - OK
afterwards
Date: Mon, 18 Jul 2005 14:56:00 +0300
Use 127.0.0.1 instead of localhost
In this case DNS is not used.
Andrus.
""Scott cox"" <sadcox66@xxxxxxxxxxx> wrote in message
news:BAY19-F8EAC399090BB16BFA5ADFCDD00@xxxxxxxxxx
>I am running PostgreSQL 8.0 on WinXP
> When I try to connect
>
> psql.exe" -h localhost -p 5432 template1 "postgres"
>
> I have to wait
> 30 seconds before the Password: Prompt arrives
> 30 seconds after the password is entered.
> Once I am connected access is fast. I figured the problem is
> Authentication.
>
> a.) I tried the following (pg_hba.conf) with no success/difference
> # TYPE DATABASE USER CIDR-ADDRESS METHOD
> #host all all 127.0.0.1/32 trust
> #local all all trust
> ## IPv4 local connections:
> #host all all 127.0.0.1/32 md5
>
> b.) Installed QoS as suggested in a post in this list. No success
>
> I am only using TCP/IP on localhost (127.0.0.1) - I am open to
> suggestions and any recommendation of tools that would let me
> figure out what is happening.
>
> TIA
> -Scott
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
