Re: Setting log_connection in connection string doesn't work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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:29:26
Message-ID: 1768713.1660746566@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2022-08-17 14:30:16 Re: Setting log_connection in connection string doesn't work
Previous Message Bruce Momjian 2022-08-17 14:23:06 Re: Setting log_connection in connection string doesn't work