Re: Logging which local address was connected to in log_line_prefix

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Greg Sabino Mullane <htamfids@gmail.com>

Cc: Jim Jones <jim.jones@uni-muenster.de>, david@pgmasters.net, Peter Eisentraut <peter@eisentraut.org>, Cary Huang <cary.huang@highgo.ca>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>

Date: 2025-04-07T15:27:19Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add local-address escape "%L" to log_line_prefix.
- 3516ea768c92 18.0 landed

Greg Sabino Mullane <htamfids@gmail.com> writes:
> On Sun, Apr 6, 2025 at 6:01 PM Tom Lane <tgl@sss.pgh.pa.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.

Hearing no other comments, I pushed 0004 as-is.  It's trivial enough
to replace "[none]" with "" if somebody makes the case for that.

			regards, tom lane