Re: Backport "WITH ... AS MATERIALIZED" syntax to <12?

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Colin Watson <cjwatson(at)canonical(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Backport "WITH ... AS MATERIALIZED" syntax to <12?
Date: 2019-10-19 04:01:04
Message-ID: 87lfthgzdk.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Michael" == Michael Paquier <michael(at)paquier(dot)xyz> writes:

> On Fri, Oct 18, 2019 at 02:21:30PM +0100, Colin Watson wrote:
>> However, an alternative would be to backport the new syntax to some
>> earlier versions. "WITH ... AS MATERIALIZED" can easily just be
>> synonymous with "WITH ... AS" in versions prior to 12; there's no
>> need to support "NOT MATERIALIZED" since that's explicitly
>> requesting the new query-folding feature that only exists in 12.
>> Would something like the attached patch against REL_11_STABLE be
>> acceptable? I'd like to backpatch it at least as far as PostgreSQL
>> 10.

Michael> I am afraid that new features don't gain a backpatch. This is
Michael> a project policy. Back-branches should just include bug fixes.

I do think an argument can be made for making an exception in this
particular case. This wouldn't be backpatching a feature, just accepting
and ignoring some of the new syntax to make upgrading easier.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2019-10-19 04:17:39 Re: jsonb_set() strictness considered harmful to data
Previous Message Noah Misch 2019-10-19 03:27:18 pgsql: For all ppc compilers, implement compare_exchange and fetch_add