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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: 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-13 14:55:22
Message-ID: CAKFQuwZWu6kQqQ4XC0XTohC5SM-mHx6MR622d=WJ2JbqDRRgRA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday, January 13, 2026, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:

>
> 1) Just document it and hope people will read the documentation and/or
> understand that it's a new feature that needs time to mature.
>

Unless experimental means we are allowed to make breaking changes in minor
releases I’d say we do the best we can and then just put it out there as
normal.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2026-01-13 14:59:12 Re: Buffer locking is special (hints, checksums, AIO writes)
Previous Message Greg Burd 2026-01-13 14:54:10 Re: Expanding HOT updates for expression and partial indexes