Re: Setting log_connection in connection string doesn't work

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Setting log_connection in connection string doesn't work
Date: 2021-10-27 01:24:05
Message-ID: 20211027.102405.1336553917010534751.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Tue, 26 Oct 2021 09:39:12 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
> Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> writes:
> > I noticed that the following command doesn't leave connection log in
> > log file.
> >> psql "host=localhost options=-c\ log_connections=on"
>
> [ shrug... ] Why would you expect it to? Should "-c log_connections=off"
> be able to hide a connection from the log?

I don't know. The fact is that it's a superuser-backend variable that
is silently ignored (but acutally seems to be set in the session).
Setting log_disconnection the same way works (of course the impliction
of this is far less significant that the log_connection case).

If we want to refuse them to be set at session start (and I think so),
shouldn't they be changed to SIGHUP? (I forgot to mention this choice
in the previous mail..)

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment Content-Type Size
change_log_connections_to_sighup.patch text/x-patch 737 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2021-10-27 01:36:35 Re: [PATCH v2] src/port/snprintf.c: Optimize the common base=10 case in fmtint
Previous Message Andres Freund 2021-10-27 00:22:15 heads up: initdb.exe now succeeds in wine