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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Subject: Re: how to gate experimental features (SQL/PGQ)
Date: 2026-01-14 20:59:02
Message-ID: 6B08AFE7-318B-458A-9CD6-5F5F160C7ADF@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 13 Jan 2026, at 18:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> It might be better just to say that you only
> get to change experimental catalog entries once a year in major
> releases. (Slow progress is still better than no progress.)

I think this idea has a lot of merit.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2026-01-14 21:01:58 Re: support ALTER COLUMN SET EXPRESSION over virtual generated column with check constraint
Previous Message Daniel Gustafsson 2026-01-14 20:57:32 Re: how to gate experimental features (SQL/PGQ)