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+hUKGKd=9WR0NvXq1rQfZyCAiiSr7R+-P2AAuimO5+f-A6BUA@mail.gmail.com
Whole thread Raw
In response to We're leaking predicate locks in HEAD  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: We're leaking predicate locks in HEAD  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Wed, May 8, 2019 at 5:46 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> After running the core regression tests with installcheck-parallel,
> the pg_locks view sometimes shows me apparently-orphaned SIReadLock
> entries. [...]

Ugh.

> I'd have to say that my first suspicion falls on bb16aba50 ...

Investigating.

-- 
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: We're leaking predicate locks in HEAD
Next
From: Tom Lane
Date:
Subject: Fuzzy thinking in is_publishable_class