Re: Weird problem that enormous locks - Mailing list pgsql-general

From Tony Wang
Subject Re: Weird problem that enormous locks
Date
Msg-id CAH1z_A4k3D4ziHYKXUEgcrkL+jg13QFkAQENaO01a+iWxUfWfg@mail.gmail.com
Whole thread Raw
In response to Re: Weird problem that enormous locks  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general
On Fri, Jul 15, 2011 at 18:44, Scott Marlowe <scott.marlowe@gmail.com> wrote:
On Fri, Jul 15, 2011 at 4:36 AM, Tony Wang <wwwjfy@gmail.com> wrote:
> Weird that I receive your each message twice.
> On Fri, Jul 15, 2011 at 15:33, Radoslaw Smogura <rsmogura@softperience.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.

pgsql-general by date:

Previous
From: Tony Wang
Date:
Subject: Re: Weird problem that enormous locks
Next
From: Tom Lane
Date:
Subject: Re: C function returns null values