| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, michael(at)paquier(dot)xyz, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Setting log_connection in connection string doesn't work |
| Date: | 2022-08-17 14:30:16 |
| Message-ID: | Yvz7eJILMVWkzsbU@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 17, 2022 at 10:29:26AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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.
Okay, thanks for the feedback.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2022-08-17 14:46:16 | Re: POC: GROUP BY optimization |
| Previous Message | Tom Lane | 2022-08-17 14:29:26 | Re: Setting log_connection in connection string doesn't work |