Re: Patch proposal: New hooks in the connection path - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Patch proposal: New hooks in the connection path
Date
Msg-id 3301034.1657287802@sss.pgh.pa.us
Whole thread Raw
In response to Re: Patch proposal: New hooks in the connection path  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> On Fri, Jul 8, 2022 at 1:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It doesn't seem like a great place for a hook, because the list of stuff
>> you could safely do there would be mighty short, possibly the empty set.

> I agree with this. But, all of the areas that v2-0003 touched for
> connectivity failures, they typically are emitting
> ereport(FATAL,/ereport(COMMERROR, (in ProcessStartupPacket) and we
> have emit_log_hook already being exposed and the implementers can,
> literally, do anything the hook.

This is utterly off-point, because those calls are not inside
signal handlers.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: Add function to return backup_label and tablespace_map
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] fix wait_event of pg_stat_activity in case of high amount of connections