From: | Tony Wang <wwwjfy(at)gmail(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Weird problem that enormous locks |
Date: | 2011-07-15 13:37:53 |
Message-ID: | CAH1z_A4k3D4ziHYKXUEgcrkL+jg13QFkAQENaO01a+iWxUfWfg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 15, 2011 at 18:44, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> On Fri, Jul 15, 2011 at 4:36 AM, Tony Wang <wwwjfy(at)gmail(dot)com> wrote:
> > Weird that I receive your each message twice.
> > On Fri, Jul 15, 2011 at 15:33, Radoslaw Smogura <
> rsmogura(at)softperience(dot)eu>
> > wrote:
> >>
> >> Simple and obvious question right now do You call commit after
> >> transaction? If yes do you use any query or connection pooler?
> >
> > Yes. connection pool is used as application level, not db level.
> > no commit after transaction is possible (I'm trying to check the logic),
> I
> > just cannot imagine it happened for so many users at the same time, and
> then
> > calmed down for long time, and came again.
> > I found the query I used to log locks would miss locks that relname is
> null.
> > will add that, though no idea why it's null
>
> They're likely exclusive locks on a transaction, which are normal.
>
Thanks for the info. May miss something without such rows.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-07-15 14:24:24 | Re: C function returns null values |
Previous Message | Tony Wang | 2011-07-15 13:30:43 | Re: Weird problem that enormous locks |