From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Subject: | Re: VACUUM (DISABLE_PAGE_SKIPPING on) |
Date: | 2021-04-08 16:29:25 |
Message-ID: | CANP8+jKRsij_p_JDHxKrP7g2U1fAys9rSk=URUZAXMOrHNc-dg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 8 Apr 2021 at 16:58, David Steele <david(at)pgmasters(dot)net> wrote:
> >> It has been five months since this patch was updated, so marking
> >> Returned with Feedback.
> >>
> >> Please resubmit to the next CF when you have a new patch.
> >
> > There are 2 separate patch-sets on this thread, with separate CF entries.
> >
> > One has requested changes that have not been made. I presume this one
> > has been RwF'd.
> >
> > What is happening about the other patch?
>
> Hmmm, well https://commitfest.postgresql.org/32/2908 and
> https://commitfest.postgresql.org/32/2909 are both linked to the same
> thread with the same patch, so I thought it was a duplicate.
Nobody had mentioned any confusion. Multiple patches on one thread is common.
> It's not clear to me which patch is which, so perhaps move one CF entry
> to next CF and clarify which patch is current?
Entry: Maximize page freezing
has this patch, perfectly fine, awaiting review from Alvaro since 29 Nov.
one_freeze_then_max_freeze.v7.patch
Other patch is awaiting changes.
--
Simon Riggs http://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2021-04-08 16:30:50 | Re: psql - add SHOW_ALL_RESULTS option |
Previous Message | Tom Lane | 2021-04-08 16:21:05 | Re: SQL-standard function body |