Re: Up to 50x degradation in dblink performance when receiving notice traffic 19 vs 18

On Fri, Sep 25, 2026 at 1:39 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> Thanks for verifying, here is a v2 version

Thanks for the patch!
+1 to calling errhidestmt(true) and errhidecontext(true).

+ /*
+ * Don't log the local statement or context. This runs once for every
+ * message the remote server sends, and LOG passes the default
+ * log_min_error_statement, so each message would otherwise repeat the
+ * whole text of whatever local query is running. The local context only
+ * says where libpq happened to be reading input, not what caused the
+ * message.
+ */

This comment sounds a bit redundant and indirect to me. How about a simpler
one like this?

Omit the local statement and context from each remote message.
They can help identify the caller, but repeating them for every
message could greatly increase log volume.

Regards,

--
Fujii Masao