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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Kai Wagner <kai(dot)wagner(at)percona(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:11:15
Message-ID: CAKFQuwbE661f3Nq=PemGmaL1Xu6rq_0djRMyG=ug3b=CFy_C3w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2026-01-14 19:14:33 Re: code contributions for 2025, WIP version
Previous Message Alexandra Wang 2026-01-14 19:08:30 Re: SQL:2023 JSON simplified accessor support