From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Chris Barnes <compuguruchrisbarnes(at)hotmail(dot)com> |
Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Locks in postgres causing system load and crash. |
Date: | 2009-09-14 15:53:08 |
Message-ID: | dcc563d10909140853u3d2b704wfcc3954b8f82f876@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Sep 14, 2009 at 8:58 AM, Chris Barnes
<compuguruchrisbarnes(at)hotmail(dot)com> wrote:
> We have a situation where the database locks escalate and load causes
> problems or the system crashes in some circumstances.
>
> We have munin installed and notice that the locks (access share locks)
> climbed to 2.7k.
>
> I'm wondering what or how I can get a snapshot of the table(s) and perhaps
> the culprit that is causing this either from postgres internally or some
> other means?
The access share locks are likely a symptom, not the cause. Look for
what they're waiting on for the lock. It's usually an exclusive lock
of some kind that causes this problem. We had an issue with a wayward
update with no where clause causing an issue like this a year ago.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-09-14 15:54:32 | Re: Checkpoint request failed, permission denied |
Previous Message | Scott Marlowe | 2009-09-14 15:46:39 | Re: Postgresql Hardware |