| From: | Marco Maccaferri <macca(at)maccasoft(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres partially hang after inactivity |
| Date: | 2009-05-07 16:30:34 |
| Message-ID: | 4A030CAA.7080504@maccasoft.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 06/05/2009 21:39 Merlin Moncure ha scritto:
> probably, you had a transaction sitting around that is not closed (to
> see: select * from pg_stat_activity).
>
> the alter table is waiting for that transaction to finish, but itself
> blocks all _new_ transactions (alter table acquires a strong lock on
> the table). Cancel the alter table query or the query that is
> blocking your alter table. Again, check pg_stat_activity and
> ungranted locks (select * from pg_locks where granted = false).
By querying these tables I found that the connection pooling was not
setup properly and that there were few unclosed sessions hanging around.
Thank you for your help.
Regards,
Marco.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-05-07 18:51:11 | Re: Optimizing tuning and table design for large analytics DB |
| Previous Message | Tom Lane | 2009-05-07 16:26:54 | Re: "No transaction in progress" warning |