Postgres Pro
Downloads
Home   >   mailing lists

Re: We're leaking predicate locks in HEAD - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: We're leaking predicate locks in HEAD
Date
Msg-id CA+hUKGLhC5u5EsKJRD5LDjo4t1W8s3ied2u9WOykS1ud4ugQ+Q@mail.gmail.com
Whole thread Raw
In response to Re: We're leaking predicate locks in HEAD  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: We're leaking predicate locks in HEAD  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Wed, May 8, 2019 at 6:56 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> On Wed, May 8, 2019 at 5:46 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > I'd have to say that my first suspicion falls on bb16aba50 ...
>
> Investigating.

Reproduced here.  Once the system reaches a state where it's leaking
(which happens only occasionally for me during installcheck-parallel),
it keeps leaking for future SSI transactions.  The cause is
SxactGlobalXmin getting stuck.  The attached fixes it for me.  I can't
remember why on earth I made that change, but it is quite clearly
wrong: you have to check every transaction, or you might never advance
SxactGlobalXmin.

-- 
Thomas Munro
https://enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: _bt_split(), and the risk of OOM before its critical section
Next
From: Etsuro Fujita
Date:
Subject: Re: postgres_fdw: another oddity in costing aggregate pushdown paths