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

From Tom Lane
Subject Re: Improve LWLock tranche name visibility across backends
Date
Msg-id 717489.1752522932@sss.pgh.pa.us
Whole thread Raw
In response to Re: Improve LWLock tranche name visibility across backends  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes:
> Ah, I missed the problem with postmaster.  Could we have the first backend
> that needs to access the table be responsible for creating it and
> populating it with the built-in/requested-at-startup entries?  Also, is
> there any chance that postmaster might need to access the tranche names?

Seems quite hazardous to let the postmaster get involved with such
a data structure.  If it seems to need to, we'd better rethink
where to put the functionality that needs the access.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Improve LWLock tranche name visibility across backends
Next
From: Nathan Bossart
Date:
Subject: fix organization wording in psql's \copyright command