| From: | Dmitri Girski <mitek17(at)gmail(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | pg_connect takes 3.0 seconds |
| Date: | 2010-01-05 02:12:53 |
| Message-ID: | daed64561001041812s602a3098l686f630d6448835f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi everybody,
I am running a PostgreSQL server 8.3.5 with a pretty much standard config.
The web application server which runs Apache 1.3/PHP2.9 has an intermittent
problem:
pg_connect takes exactly 3.0 seconds. The usual connection time is 0.0045.
The long request happens at approximate rate 1:100.
I turned on logs on postgres server side, and there is
nothing suspicious for me there. When a connection request comes, it is
being served without any delay.
Could anyone point me to the direction in which I should investigate this
problem further?
Thank you in advance!
PS The hardware is: Dell SC1435/4Gb/2x2.0GHz/Gentoo Linux.
The database & web servers are in the 2 local subnets.
Dmitri.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-01-05 02:14:00 | Re: forced sequential scan when condition has current_user |
| Previous Message | Robert Haas | 2010-01-05 02:09:00 | Re: forced sequential scan when condition has current_user |