| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andy Colson <andy(at)squeakycode(dot)net>, <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 22:08:41 |
| Message-ID: | 543312E9.4060307@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/6/14, 10:15 AM, Andy Colson wrote:
> 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)
FYI, 8.3 is almost 7 years old and is no longer supported. I strongly suggest that you upgrade to something more recent.
>> E.g., got 10 idle connections for 10 days.
>
> idle is ok. It wastes a little extra ram, but wont hurt anything. "idle in transaction" for long periods of time is bad.
It's more than just memory. Each connection has a slot in the proc array and there's places in the code that are pretty sensitive to how big that array gets. There's some other structures that have this issue as well. 10 extra connections won't mean much; 1000 certainly would.
--
Jim Nasby, Data Architect, Blue Treble
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-10-06 22:15:08 | Re: Really strange foreign key constraint problem blocking delete |
| Previous Message | Jim Nasby | 2014-10-06 22:00:12 | Re: Processor usage/tuning question |