| From: | Oliver Kohll - Mailing Lists <oliver(dot)lists(at)gtwm(dot)co(dot)uk> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Cc: | Frank Lanitz <frank(at)frank(dot)uvena(dot)de> |
| Subject: | Re: Index creation problem |
| Date: | 2012-10-19 12:52:50 |
| Message-ID: | E83F9402-5791-482C-AD50-FFC3A7EEC5D5@gtwm.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 19 Oct 2012, at 13:28, Frank Lanitz <frank(at)frank(dot)uvena(dot)de> wrote:
> Just an idea without bigger investigation: Whare are the idle in
> transactions are doing? Maybe they are blocking the create index.
>
> Cheers,
> Frank
Good question, I don't know. The app runs on Java / Apache Tomcat, which maintains a connection pool, so I assumed the IDLEs were just opened connections but I didn't notice two were idle in transaction. I haven't dealt with this before but this looks like a good explanation:
http://www.depesz.com/2008/08/28/hunting-idle-in-transactions/
I will up logging and try to replicate. Next time I will look at pg_locks too.
Also, the PG version is 9.1.6.
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | GMAIL | 2012-10-19 13:02:51 | Multiple Cluster on same host |
| Previous Message | Albe Laurenz | 2012-10-19 12:43:23 | Re: Index creation problem |