Re: Emit a warning if the extension's GUC is set incorrectly

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com
Cc: peter(dot)eisentraut(at)enterprisedb(dot)com, masao(dot)fujii(at)oss(dot)nttdata(dot)com, bharath(dot)rupireddyforpostgres(at)gmail(dot)com, daniel(at)yesql(dot)se, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Emit a warning if the extension's GUC is set incorrectly
Date: 2021-12-21 01:08:34
Message-ID: 20211221.100834.1297468238807011575.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Mon, 20 Dec 2021 21:05:23 +0900, Shinya Kato <Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com> wrote in
> - v6-01-Add-EmitWarningsOnPlaceholders.patch
> We should use EmitWarningsOnPlaceholders when we use
> DefineCustomXXXVariable.
> I don't think there is any room for debate.

Unfortunately, pltcl.c defines variables both in pltcl and pltclu but
the patch adds the warning only for pltclu.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-12-21 01:17:26 Re: do only critical work during single-user vacuum?
Previous Message Tom Lane 2021-12-21 01:01:59 Re: sequences vs. synchronous replication