Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, gavinpanella(at)gmail(dot)com
Subject: Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs
Date: 2023-10-18 05:15:11
Message-ID: 3046870.1697606111@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrei Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> writes:
> "SET foo.bar TO 'smth'" can immediately alter the placeholder's value.
> But what is the reason that "ALTER SYSTEM SET foo.bar TO 'smth'" doesn't
> do the same?

Because it's not supposed to take effect until you issue a reload
command (and maybe not even then, depending on which GUC we're
talking about). I certainly think it wouldn't make sense for your
own session to adopt the value ahead of others.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii.Yuki@df.MitsubishiElectric.co.jp 2023-10-18 05:22:34 RE: Partial aggregates pushdown
Previous Message Andrei Lepikhov 2023-10-18 04:55:48 Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs