| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logging which interface was connected to in log_line_prefix |
| Date: | 2024-05-12 12:21:15 |
| Message-ID: | 4852776b-ed8b-4a39-80ee-86223fe6d389@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 캔SQL : |
On 06.03.24 16:59, Greg Sabino Mullane wrote:
> Someone on -general was asking about this, as they are listening on
> multiple IPs and would like to know which exact one clients were
> hitting. I took a quick look and we already have that information, so I
> grabbed some stuff from inet_server_addr and added it as part of a "%L"
> (for 'local interface'). Quick patch / POC attached.
I was confused by this patch title. This feature does not log the
interface (like "eth0" or "lo"), but the local address. Please adjust
the terminology.
I noticed that for Unix-domain socket connections, %r and %h write
"[local]". I think that should be done for this new placeholder as well.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-05-12 12:25:24 | Re: Logging which interface was connected to in log_line_prefix |
| Previous Message | Peter Eisentraut | 2024-05-12 11:57:43 | Re: [PATCH] Replace magic constant 3 with NUM_MERGE_MATCH_KINDS |