| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | Uwe Schroeder <uwe(at)oss4u(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: virtualidx exclusive lock |
| Date: | 2009-11-09 18:00:53 |
| Message-ID: | 4AF858D5.3090602@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Uwe Schroeder wrote:
> I've googled, but there's 0 hits.
>
> I have an issue with a ton of "idle in transaction" backends.
> What I noticed is when I look at pg_locks, pretty much all of the processes being idle in transaction have an exclusive lock of locktype "virtualidx
>
"Idle in Transaction" occurs when a client has issued a BEGIN; and is
then just sitting there.
We had this problem extensively with our Java code some years back when
the PostgreSQL JDBC module was issuing a BEGIN; right after a COMMIT or
ROLLBACK when not in autocommit mode. An updated version of JDBC
postponed this automatic BEGIN until the first command was issued.
Since we had some connections which would sit idle for hours, this would
prevent VACUUM from cleaning anything newer than the oldest pending
transaction.
.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-11-09 18:03:45 | Re: Not possible to create 64 bit windows clients ? |
| Previous Message | John R Pierce | 2009-11-09 17:23:31 | Re: I can't seem to put the right combination of magic into the pg_hba and pg_ident files. |