From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, michael@paquier.xyz,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Setting log_connection in connection string doesn't work
In-reply-to: <Yvz5yjAVo/xgCWpP@momjian.us>
References: <80426.1635255552@sss.pgh.pa.us>
 <20211027.102405.1336553917010534751.horikyota.ntt@gmail.com>
 <YXixkyUXQH9/BSKO@paquier.xyz>
 <20211027.115309.1302464757802948949.horikyota.ntt@gmail.com>
 <Yvz5yjAVo/xgCWpP@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Wed, 17 Aug 2022 10:23:06 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1768712.1660746566.1@sss.pgh.pa.us>
Date: Wed, 17 Aug 2022 10:29:26 -0400
Message-ID: <1768713.1660746566@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1768713.1660746566%40sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> This patch is from October of 2021.  I don't see any commitfest entry
> for it.  Should it be applied?

I think we decided not to.  The original argument for having these
be PGC_SU_BACKEND was to try to ensure that you got matching
connection and disconnection log entries for any one session,
and I don't see anything that supersedes that plan.

			regards, tom lane