Re: [PATCH] Expose port->authn_id to extensions and triggers - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: [PATCH] Expose port->authn_id to extensions and triggers
Date
Msg-id 20220225050126.f5io3k22czloilel@jrouhaud
Whole thread Raw
In response to Re: [PATCH] Expose port->authn_id to extensions and triggers  (Jacob Champion <pchampion@vmware.com>)
Responses Re: [PATCH] Expose port->authn_id to extensions and triggers
List 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.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations
Next
From: Andres Freund
Date:
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers