| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Sergey Dudoladov <sergey(dot)dudoladov(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Subject: | Re: Introduce "log_connection_stages" setting. |
| Date: | 2025-03-12 15:48:19 |
| Message-ID: | CAAKRu_Zqx-rjcqfxwkDoqLy05xFZ1mq-Q1cvhaDV84re2dFV+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 3, 2025 at 6:43 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> Okay, I got cold feet today working on this. I actually think we
> probably want some kind of guc set (set like union/intersection/etc
> not set like assign a value) infrastructure for gucs that can be equal
> to any combination of predetermined values.
I ended up with a patch set that I was happy with which used the list
of string GUCs. I committed it in 9219093cab26. It changes
log_connections to a list of strings for the different aspects of
connection setup and supports the most common inputs for the boolean
version of log_connections for backwards compatibility. I did not end
up deprecating log_disconnections since it is rather late in the cycle
and that change could use more visibility. I suggest proposing that at
the beginning of the next release.
Thanks for your interest in this topic.
- Melanie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2025-03-12 15:48:45 | Re: Non-text mode for pg_dumpall |
| Previous Message | Melanie Plageman | 2025-03-12 15:43:17 | Re: Log connection establishment timings |