From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parallel vacuum workers prevent the oldest xmin from advancing |
Date: | 2021-11-10 12:11:56 |
Message-ID: | CAEze2WhhoTPRaHwS+PtA4D+2pipfPJpVR5HuMjJM2iWH3f3GRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 10 Nov 2021 at 11:51, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Fri, Nov 5, 2021 at 8:16 PM Matthias van de Meent
> <boekewurm+postgres(at)gmail(dot)com> wrote:
>
> AFAICU, in the thread referred by you, it seems that the main reported
> issue will be resolved by this patch but there is a discussion about
> xmin moving backward which seems to be the case with the current code
> as per code comments mentioned by Andres. Is my understanding correct?
That is correct.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-11-10 12:14:30 | Re: standby recovery fails (tablespace related) (tentative patch and discussion) |
Previous Message | Alvaro Herrera | 2021-11-10 12:09:03 | Re: prevent immature WAL streaming |