> On 13 Jan 2026, at 15:16, Peter Eisentraut <peter@eisentraut.org> wrote:
> 2) A run-time setting (GUC) like experimental_pgq = on/off. This would be checked in the relevant DDL
(CREATE/ALTER/DROP)commands as well as the GRAPH_TABLE function. So without that you couldn't do anything with it, but
forexample pg_dump and psql and ecpg preproc would still work and the system catalogs exist. Default to off for one
release(subject to change).
Such a GUC would IMHO only make sense if we remove it when we promote the
feature, but removing a GUC also comes with a cost for anyone having baked it
into their scripts etc. If we feel confident enough that a patch satisfies the
security requirements to merge it, I think we should make it available.
If a feature is deemed experimental in terms of it being feature completeness
(missing parts etc), or because user visible parts might change, then the
documentation is IMO the vehicle for handling that.
--
Daniel Gustafsson
