| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Colin Watson <cjwatson(at)canonical(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Backport "WITH ... AS MATERIALIZED" syntax to <12? |
| Date: | 2019-10-19 02:34:03 |
| Message-ID: | 20191019023403.GD1542@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
I am afraid that new features don't gain a backpatch. This is a
project policy. Back-branches should just include bug fixes.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-10-19 02:41:06 | Re: v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock on object 14185/39327/0 is already held |
| Previous Message | Michael Paquier | 2019-10-19 02:28:59 | Re: recovery_min_apply_delay in archive recovery causes assertion failure in latch |