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

From Andrew Dunstan
Subject Re: We're leaking predicate locks in HEAD
Date
Msg-id 9a2d396e-85d9-bef5-ab0b-0d1007f0ff3a@2ndQuadrant.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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5/7/19 1:46 PM, Tom Lane wrote:
> After running the core regression tests with installcheck-parallel,
> the pg_locks view sometimes shows me apparently-orphaned SIReadLock
> entries.  They accumulate over repeated test runs.  


Should we have a test for that run at/near the end of the regression
tests? The buildfarm will actually do multiple runs like this if set up
to do parallel checks and test multiple locales.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: PG12, PGXS and linking pgfeutils
Next
From: Tom Lane
Date:
Subject: Re: We're leaking predicate locks in HEAD