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

From: Kai Wagner <kai(dot)wagner(at)percona(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Subject: Re: how to gate experimental features (SQL/PGQ)
Date: 2026-01-14 19:52:57
Message-ID: CAG0qCNhuF=OxS_XJ4cfpr24OHVH2jXQSY1uTf2dYTi-W+hMC8Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 14, 2026 at 8:11 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wednesday, January 14, 2026, Kai Wagner <kai(dot)wagner(at)percona(dot)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 in the 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.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2026-01-14 19:53:42 Re: Use CASEFOLD() internally rather than LOWER()
Previous Message Corey Huinker 2026-01-14 19:41:34 Re: Import Statistics in postgres_fdw before resorting to sampling.