Re: PG 14 release notes, first draft

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 14 release notes, first draft
Date: 2021-05-18 14:51:00
Message-ID: CAH2-Wzn_sZ17x4L40JuQ8VgdW-NrNfwL19HSUDx+qnZAHf3-=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 18, 2021 at 7:44 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> As things stand, in this case I think it *should* be included, since the
> backpatched change isn't the same as the change to HEAD (removing the GUC).
> The git_changelog output might well be wrong in this case (or, arguably, the
> "remove the GUC entirely" should've been a separate master-only commit than the
> "make the GUC do nothing" commit).

I suppose that's true -- maybe it should be listed separately, because
the GUC is removed in 14 only.

> However, Peter indicated an intent to add a reloption to disable the vacuum
> optimization, so maybe the removal of the GUC could be documented at that time.

This is unrelated to the bypass indexes in VACUUM thing.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-05-18 14:53:45 Re: allow specifying direct role membership in pg_hba.conf
Previous Message Justin Pryzby 2021-05-18 14:44:09 Re: PG 14 release notes, first draft