Re: Set notice receiver before libpq connection startup

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Set notice receiver before libpq connection startup
Date: 2026-05-27 17:56:50
Message-ID: 2620a664-7b44-48b2-9aa8-5f0131702d9c@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.05.26 01:56, Chao Li wrote:
>
>
>> On May 22, 2026, at 23:28, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>>
>> On Fri, May 22, 2026 at 11:56 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>>> PFA v4, just removed conn NULL check.
>>
>> Thanks for updating the patch! I've pushed it.
>>
>> Regards,
>>
>> --
>> Fujii Masao
>
> Thanks for pushing and still working hard during the PGConf.

The committed patch violates the .gitattributes whitespace rules:

git show --check 06a5c3cdef02

contrib/postgres_fdw/connection.c:651: indent with spaces.
+ /* expand_dbname =
*/ false);

It is unfortunate that pgindent produces this layout that contradicts
the git configuration. (The current formatting also doesn't look like
what I would produce in an editor, so I think git is right here.)

Maybe we could reformat this slightly to avoid that? (unless someone
wants to try to fix pgindent)

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Alexandra Wang 2026-05-27 17:49:44 Re: Is there value in having optimizer stats for joins/foreignkeys?