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

From Kai Wagner
Subject Re: how to gate experimental features (SQL/PGQ)
Date
Msg-id CAG0qCNhuF=OxS_XJ4cfpr24OHVH2jXQSY1uTf2dYTi-W+hMC8Q@mail.gmail.com
Whole thread Raw
In response to Re: how to gate experimental features (SQL/PGQ)  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Wed, Jan 14, 2026 at 8:11 PM David G. Johnston
<david.g.johnston@gmail.com> wrote:
>
> On Wednesday, January 14, 2026, Kai Wagner <kai.wagner@percona.com> wrote:
>>
>>
>> For the actual timing, this should occur as part of the major release.
>> We should definitely avoid incorporating experimental features into
>> minor updates, as this contradicts the overall stability and concept
>> of the current major updates.
>>
>
> That wasn’t the idea though.  What is your opinion on changing the behavior of an experimental feature added in 19.0
inthe 19.4 release so long as it doesn’t require initdb? 
>
Perhaps I wasn't fully clear with my statement, but I was referring to
introducing new experimental features, not adjusting/fixing/improving
existing and already shipped experimental features. That, of course,
is and should be part of a minor update, as you don't want to wait
another year for actual fixes and improvements to land for existing
ones.

Kai
> David J.
>



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Import Statistics in postgres_fdw before resorting to sampling.
Next
From: Jeff Davis
Date:
Subject: Re: Use CASEFOLD() internally rather than LOWER()