Re: Improve LWLock tranche name visibility across backends - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Improve LWLock tranche name visibility across backends
Date
Msg-id CAA5RZ0v4kwF06o4a+Xybd++ipC7TYkn879Wz_2BZK412+ULXgg@mail.gmail.com
Whole thread Raw
In response to Re: Improve LWLock tranche name visibility across backends  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Improve LWLock tranche name visibility across backends
List pgsql-hackers


I am not sure we need to do anything about this.

Or maybe we just avoid the tranche_id from leaking 
in test_dsa_resowners() by making it a static variable 
and checking if we have a valid tranche id before calling 
LWLockNewTrancheId()? That is the proper pattern.

--
Sami

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Fully documenting the design of nbtree row comparison scan keys
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: List TAP test files in makefiles