| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improve LWLock tranche name visibility across backends |
| Date: | 2025-07-16 23:17:02 |
| Message-ID: | CAA5RZ0uQ6kbwCBXzcAueqAAQ9AhQ2AjGf2CtY3AY1V19421=sw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-07-16 23:35:00 | Re: libpq: Process buffered SSL read bytes to support records >8kB on async API |
| Previous Message | Sami Imseih | 2025-07-16 22:58:28 | Re: track generic and custom plans in pg_stat_statements |