Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Thunder <thunder1(at)126(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node
Date: 2020-01-21 03:15:14
Message-ID: CAA4eK1JiWCyxmbTS93RkBS45kX4sSqvru-gL1GDABR2gkazenw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 21, 2020 at 6:05 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Jan 20, 2020 at 02:13:53PM +0530, Amit Kapila wrote:
> > Are we planning to do something about the original problem reported in
> > this thread?
>
> We should. This is on my TODO list, though seeing that it involved
> full_page_writes=off I drifted a bit away from it.
>

The original email doesn't say so. I might be missing something, but
can you explain what makes you think so.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-01-21 04:39:07 Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node
Previous Message Michael Paquier 2020-01-21 03:05:57 Re: Physical replication slot advance is not persistent