From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Modernizing our GUC infrastructure
Date: Mon, 05 Sep 2022 19:50:22 -0400
Message-ID: <2994556.1662421822@sss.pgh.pa.us> (raw)
In-Reply-To: <20220905233233.jhcu5jqsrtosmgh5@awork3.anarazel.de>
References: <2982579.1662416866@sss.pgh.pa.us>
<20220905233233.jhcu5jqsrtosmgh5@awork3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> It's only half related, but since we're talking about renovating guc.c: I
> think it'd be good if we split the list of GUCs from the rest of the guc
> machinery. Both for humans and compilers it's getting pretty large. And
> commonly one either wants to edit the definition of GUCs or wants to edit the
> GUC machinery.
I don't mind doing that, but it seems like an independent patch.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, pgsql-hackers@lists.postgresql.org
Subject: Re: Modernizing our GUC infrastructure
In-Reply-To: <2994556.1662421822@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox