On Thu, Nov 5, 2009 at 7:16 AM, Vladimir Rusinov <vladimir@xxxxxxxxxxxxxx> wrote: > > > On Tue, Nov 3, 2009 at 5:54 PM, Lewis Kapell <lkapell@xxxxxxxxxxxxx> wrote: >> >> Please see these earlier threads: >> >> Is IDLE session really idle? >> http://archives.postgresql.org/pgsql-admin/2009-06/msg00096.php >> >> Idle connections >> http://archives.postgresql.org/pgsql-admin/2009-10/msg00017.php > > 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. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
