| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter(at)berghold(dot)net |
| Cc: | General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Idle in transaction state. |
| Date: | 2006-09-10 00:49:34 |
| Message-ID: | 22969.1157849374@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc |
"Peter L. Berghold" <Peter(at)berghold(dot)net> writes:
> What I'm seeing is the first time my web application is being run there
> is a bunch of processes running around that look like:
> "postgres: peter peter_trialdb 127.0.0.1(46222) idle"
"idle" is fine, "idle in transaction" is not so fine, because those
might be holding locks that block things like schema changes. You need
to figure out why your client-side code isn't closing out its
transactions promptly.
You'd probably be better off asking on the pgsql-jdbc list about this,
as the folks likely to know about Java-stack issues hang out there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-10 00:57:00 | Re: Is this logical? |
| Previous Message | Jack Orenstein | 2006-09-10 00:33:50 | How to use SPI_saveplan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jack Orenstein | 2006-09-10 04:12:37 | Re: Idle in transaction state. |
| Previous Message | Dave Cramer | 2006-09-09 22:36:18 | Re: Idle in transaction state. |