| 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-03-26 17:14:43 |
| Message-ID: | CAKAnmmLKiYT_vUfDejH8OKheTwU+DGQztH5zMTbWsJ_=4p3P2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks for all the feedback. Please find attached a version which prints
"[none]" as the default value, "[local]" for a socket, and otherwise
whatever pg_getnameinfo_all spits out. I cleaned up the coding, respected
padding, removed the family checks, and expanded the docs a tiny bit to
give the reader more context as to what "local address" means. I also
looked into alternatives to the term "local address" but that still seems
the most correct and commonly used term.
I have not attempted the caching change yet.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| Attachment | Content-Type | Size |
|---|---|---|
| 0003-Add-local-address-to-log_line_prefix.patch | application/octet-stream | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Shaplov | 2025-03-26 17:29:17 | Re: vacuum_truncate configuration parameter and isset_offset |
| Previous Message | Sri Keerthi | 2025-03-26 17:06:52 | Deadlock detected while executing concurrent insert queries on same table |