| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | rihad(at)mail(dot)ru |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: deadlock |
| Date: | 2008-04-03 16:51:05 |
| Message-ID: | dcc563d10804030951m5b26c27ifd16591da7287523@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 3, 2008 at 10:29 AM, rihad <rihad(at)mail(dot)ru> wrote:
> Hi,
>
> I've come across a strange deadlock that I need your help with. There are
> two copies of the same Perl daemon running on a 2 cpu box. The program is
> pretty simple (because I wrote it :)) so I can trace its pathway fairly
> well: in it, there's a single "LOCK table foo" occurring part way through a
> transaction that sometimes ends up as this:
For what reason is the table being locked?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2008-04-03 16:51:24 | Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong |
| Previous Message | William Temperley | 2008-04-03 16:50:39 | Secure "where in(a,b,c)" clause. |