Re: SQL/JSON features for v15 - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: SQL/JSON features for v15
Date
Msg-id Yw+nmKq3omnj61MD@momjian.us
Whole thread Raw
In response to Re: SQL/JSON features for v15  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Aug 31, 2022 at 12:04:44PM -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > From my POV the only real discussion is whether we'd want to revert this in 15
> > and HEAD or just 15. There's imo a decent point to be made to just revert in
> > 15 and aggressively press forward with the changes posted in this thread.
> 
> I'm not for that.  Code that we don't think is ready to ship
> has no business being in the common tree, nor does it make
> review any easier to be looking at one bulky set of
> already-committed patches and another bulky set of deltas.

Agreed on removing from PG 15 and master --- it would be confusing to
have lots of incomplete code in master that is not in PG 15.

> I'm okay with making an exception for the include/nodes/ and
> backend/nodes/ files in HEAD, since the recent changes in that
> area mean it'd be a lot of error-prone work to produce a reverting
> patch there.  We can leave those in as dead code temporarily, I think.

I don't have an opinion on this.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: SQL/JSON features for v15
Next
From: Peter Geoghegan
Date:
Subject: Re: effective_multixact_freeze_max_age issue