| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Чумак Антон <a(dot)chumak(at)postgrespro(dot)ru>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Introduce unified support for composite GUC options |
| Date: | 2025-09-23 05:02:20 |
| Message-ID: | 3022888.1758603740@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> As you note - moving runtime checks to "SET" time has value and this patch
> brings that value. But it is not evident there is enough value to take on
> the added complexity. There are few to no requests asking for this ability.
If anything, I'd say we have decades of experience showing that early
checking of GUC values creates more problems than it solves. There
are too many cases where necessary context is not available at the
time of setting the value. Particularly, CREATE FUNCTION ... SET
and ALTER DATABASE/USER ... SET are problematic for this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alena Vinter | 2025-09-23 05:04:04 | Re: Resetting recovery target parameters in pg_createsubscriber |
| Previous Message | shveta malik | 2025-09-23 04:59:18 | Re: Improve pg_sync_replication_slots() to wait for primary to advance |