From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Jacob Champion <pchampion(at)vmware(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "sfrost(at)snowman(dot)net" <sfrost(at)snowman(dot)net> |
Subject: | Re: [PATCH] Expose port->authn_id to extensions and triggers |
Date: | 2022-02-25 05:01:26 |
Message-ID: | 20220225050126.f5io3k22czloilel@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 24, 2022 at 08:44:08PM +0000, Jacob Champion wrote:
>
> Yeah... I was following a similar track with the initial work last
> year, but I dropped it when the cost of implementation started to grow
> considerably. At the time, though, it looked like some overhauls to the
> stats framework were being pursued? I should read up on that thread.
Do you mean the shared memory stats patchset? IIUC this is unrelated, as the
beentry stuff Michael was talking about is a different infrastructure
(backend_status.[ch]), and I don't think there are any plans to move that to
dynamic shared memory.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-02-25 05:18:26 | Re: [PATCH] Expose port->authn_id to extensions and triggers |
Previous Message | Peter Geoghegan | 2022-02-25 04:53:08 | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |