Re: fix special case during recovery for hot_standby=off

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: fix special case during recovery for hot_standby=off
Date: 2026-11-19 04:09:57
Message-ID: 63d2fd84e46de65c73329c5b47f8580243ce630f.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2026-11-11 at 16:26 +0530, Ayush Tiwari wrote:
> Thanks for the report. I tried this on master and could still see the
> row after promotion, even though recovery stopped before the commit.
> With your patch, recovery rejects that target instead with "requested
> recovery stop point is before consistent recovery point".
>
> This was with hot_standby=off, reusing the standby's data directory
> after a crash. I used a lot of subxacts to get the CLOG page evicted
> during replay.

Thank you for looking at it. Committed.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joao Rito 2026-11-19 04:15:26 [PATCH v2] doc: Fix autovacuum_max_workers and autovacuum_worker_slots descriptions
Previous Message Jeff Davis 2026-11-19 04:07:11 Re: pg_upgrade doesn't copy ICU rules on template0