Re: Logging which local address was connected to in log_line_prefix

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, david(at)pgmasters(dot)net, Peter Eisentraut <peter(at)eisentraut(dot)org>, Cary Huang <cary(dot)huang(at)highgo(dot)ca>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Logging which local address was connected to in log_line_prefix
Date: 2025-04-07 00:49:50
Message-ID: CAKAnmmKQfoud2PjWtY6j4BhgpKhimbCMZry_NXq7UDtT2TFPDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: Postg젠 토토SQL :

On Sun, Apr 6, 2025 at 6:01 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 1. Ignore the inconsistency, commit 0004 as-is.
>
> 2. Change the output to be an empty string in background processes.
> This is consistent, but it goes against our upthread feeling that
> "[none]" would avoid confusion.
>

I lean for #1. Yes, there is some inconsistency, but it feels like the
right thing to do, and this is a feature I suspect not many people will use
anyway.

--
Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-04-07 00:54:46 Re: per backend WAL statistics
Previous Message David G. Johnston 2025-04-07 00:43:39 Re: Possibly hard-to-read message