Re: how to gate experimental features (SQL/PGQ) - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: how to gate experimental features (SQL/PGQ)
Date
Msg-id CAKFQuwa4yr0A_GH20UH2AS7biKTbsy0xi_pNak-tZfZ3MNTwJQ@mail.gmail.com
Whole thread Raw
In response to Re: how to gate experimental features (SQL/PGQ)  (Daniel Gustafsson <daniel@yesql.se>)
List 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.
 

pgsql-hackers by date:

Previous
From: Henson Choi
Date:
Subject: Re: Row pattern recognition
Next
From: Álvaro Herrera
Date:
Subject: Re: remove the unneeded header file math.h in binaryheap.c