Downloads
Home   >   mailing lists

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 CAA5RZ0uQ6kbwCBXzcAueqAAQ9AhQ2AjGf2CtY3AY1V19421=sw@mail.gmail.com
Whole thread Raw
In response to Re: Improve LWLock tranche name visibility across backends  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
Tree view

> Hi,
>
> If a dshash table is used to store tranche names and IDs, where would the
> tranche name for this table
> be registered?

I guess it could be a new BuiltinTrancheId for this dsa but not sure what Nathan
and Sami have in mind.

Yes, it will be a BuiltinTrancheId for a shared memory that is allocated 
during postmaster for tracking tranches. The shared memory will then 
only be used by normal backends to register tranches. Any tranche 
registered during postmaster is inherited by the backends. 

Regards,

Sami 

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: track generic and custom plans in pg_stat_statements
Next
From: Andres Freund
Date:
Subject: Re: libpq: Process buffered SSL read bytes to support records >8kB on async API