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

From Bharath Rupireddy
Subject Re: Patch proposal: New hooks in the connection path
Date
Msg-id CALj2ACVCpL=CsBef9zMv2M-+hmAbjmXuXC7Wfr=7cpR50sYt-Q@mail.gmail.com
Whole thread Raw
In response to Re: Patch proposal: New hooks in the connection path  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Patch proposal: New hooks in the connection path
List pgsql-hackers
On Fri, Jul 8, 2022 at 5:54 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> Looking at v2-0003 patch and emit_log_hook, how about we filter out
> for those connectivity errors either based on error codes and if they
> aren't unique, perhaps passing special flags to ereport API indicating
> that it's a connectivity error and in the emit_log_hook we can look
> for those connectivity error codes or flags to collect the stats about
> the failure connections (with MyProcPort being present in
> emit_log_hook)? This way, we don't need a new hook. Thoughts?

Bertrand and Other Hackers, above comment may have been lost in the
wild - any thoughts on it?

Regards,
Bharath Rupireddy.



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: optimize lookups in snapshot [sub]xip arrays
Next
From: Richard Guo
Date:
Subject: Re: remove_useless_groupby_columns is too enthusiastic