From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: michael@paquier.xyz
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Setting log_connection in connection string doesn't work
Date: Wed, 17 Aug 2022 10:29:26 -0400
Message-ID: <1768713.1660746566@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, 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: <1768713.1660746566@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox