From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Tony Wang <wwwjfy(at)gmail(dot)com> |
Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Weird problem that enormous locks |
Date: | 2011-07-15 10:44:19 |
Message-ID: | CAOR=d=2=VERQ=kS3zU_5pBjb1rujgqr-ReQsd891EJr1muY7LQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Radosław Smogura | 2011-07-15 10:50:19 | Re: Weird problem that enormous locks |
Previous Message | Tony Wang | 2011-07-15 10:36:19 | Re: Weird problem that enormous locks |