| From: | Andy Colson <andy(at)squeakycode(dot)net> |
|---|---|
| To: | emilu(at)encs(dot)concordia(dot)ca, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: <idle> question |
| Date: | 2014-10-06 15:15:44 |
| Message-ID: | 5432B220.50408@squeakycode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/6/2014 10:07 AM, Emi Lu wrote:
> Hello List,
>
> May I know will <idle> cause any potential performance issues for
> psql8.3 please?
> version (PostgreSQL 8.3.18 on x86_64-unknown-linux-gnu, compiled by GCC
> 4.1.2)
>
> E.g., got 10 idle connections for 10 days.
> select current_query from pg_stat_activity where usename ='test';
> current_query
> --------------------------------------------------------------------------
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
> <IDLE>
>
> Thanks a lot!
> Emi
idle is ok. It wastes a little extra ram, but wont hurt anything.
"idle in transaction" for long periods of time is bad.
-Andy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Mickelson | 2014-10-06 15:25:08 | Re: Really strange foreign key constraint problem blocking delete |
| Previous Message | Merlin Moncure | 2014-10-06 15:10:47 | Re: How to find greatest record before known values fast |