| From: | Robert Becker Cope <robert(at)gonkgonk(dot)com> |
|---|---|
| To: | bhurt(at)janestcapital(dot)com, pgsql-performance(at)postgresql(dot)org, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Postgres locking up? |
| Date: | 2006-09-30 00:53:46 |
| Message-ID: | OF7BFE9B02.F9B5036D-ON862571F9.0004ECA0@bytestacker.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Brian Hurt <bhurt(at)janestcapital(dot)com> wrote:
> I'm experiencing a problem with our postgres database. Queries that
> normally take seconds suddenly start taking hours, if they complete at
> all.
Do you have any long running transactions? I have noticed that with Postgres
8.1.x, a long running transaction combined with other transactions over a long
enough time period can very predictably lead to this type of behavior
One simple way to see if you have any long running transactions is to look for
PIDs that are "idle in transaction" for long periods of time.
robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nimesh Satam | 2006-09-30 09:25:54 | Table not getting vaccumed. |
| Previous Message | Tom Lane | 2006-09-29 21:58:52 | Re: cont. how to optimize postgres 8.1 |