On Thu, Nov 5, 2009 at 7:16 AM, Vladimir Rusinov
> On Tue, Nov 3, 2009 at 5:54 PM, Lewis Kapell <lkapell(at)setonhome(dot)org> wrote:
>> Please see these earlier threads:
>> Is IDLE session really idle?
>> Idle connections
> Thanks - that was useful reading, but not related to my issue. There are not
> a lot of IDLE sessions: connection pools are configured accurate. There are
> problems with 'IDLE in transaction' sessions, which I believe may cause
> strong lock problems.
The real issue with idle in transaction isn't locking so much. A
simple idle in transaction that just ran a select * from table limit
1; will have made it so that vacuum cannot reclaim space that it
normally could until that transaction is committed or rolled back. So
it's much worse than simple locking of a few records, it's causing
your data store to bloat with all the otherwise reclaimable space
since that transaction began. Let it run for a day or a week and a
busy database will be expanding until it's slow and possibly running
out of space.
In response to
pgsql-admin by date
|Next:||From: Alvaro Herrera||Date: 2009-11-05 17:57:52|
|Subject: Re: fighting '<IDLE> in transaction'|
|Previous:||From: Kevin Grittner||Date: 2009-11-05 16:40:01|
|Subject: Re: pg_stat_activity howto|