Re: BUG #12469: pg_locks shows locks held by pids not found i n pg_stat_activity or ps

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #12469: pg_locks shows locks held by pids not found i n pg_stat_activity or ps
Date: 2015-01-09 18:38:36
Message-ID: 850420152.4245057.1420828716461.JavaMail.yahoo@jws100171.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Karl O. Pinc <kop(at)meme(dot)com> wrote:
> Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:

>> The short explanation is that SIReadLocks on a serializable
>> transaction may need to be kept until overlapping transactions
>> terminate.
>
> The transactions/locks are in separate databases. I would think
> that in most cases that a
> transaction in one database cannot have any effect on a
> transaction in another database.
>
> It would be nice if pg were clever enough to isolate transactions
> within databases.

Good point. That would complicate the logic a bit, but it might be
worth it. I'll make a note to look at that as a potential
enhancement. Thanks!

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marko Tiikkaja 2015-01-09 18:44:28 Re: BUG #12469: pg_locks shows locks held by pids not found i n pg_stat_activity or ps
Previous Message Karl O. Pinc 2015-01-09 18:31:46 Re: BUG #12469: pg_locks shows locks held by pids not found i n pg_stat_activity or ps