Horton

Re: how to gate experimental features (SQL/PGQ)

David G. Johnston <david.g.johnston@gmail.com>

View thread View on postgr.es
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Peter Eisentraut <peter@eisentraut.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Date: 2026-01-15T13:29:19Z
Lists: pgsql-hackers 
On Wednesday, January 14, 2026, Daniel Gustafsson <daniel@yesql.se> wrote:

>
> 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.


The very nature of experimental, that one must accept having to modify
their applications during any given minor release, nullifies this concern.
You know when you set the value to true you will have to remove that
command potentially at the next major release.  It’s part of the bargain.

David J.