Re: Change checkpoint‑record‑missing PANIC to FATAL

From: Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change checkpoint‑record‑missing PANIC to FATAL
Date: 2026-07-23 10:56:28
Message-ID: CAMm1aWZhufkxhjn8ZcZvYEPCjrDH6WFiREOR7EPJDSYuTcDyKA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Nay. At this point I am happy with the state of the test on HEAD. If
> there is a need for a refactoring piece in the future, we could always
> reconsider this piece at a later point.

Thanks, that makes sense to me.

Best Regards,
Nitin Jadhav
Azure Database for PostgreSQL
Microsoft

On Wed, Jul 22, 2026 at 3:58 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jul 21, 2026 at 04:17:17PM +0530, Nitin Jadhav wrote:
> > I don't think that's necessary anymore. Those helpers were primarily
> > introduced to support the second test, and with the revised approach I
> > don't see a strong reason to make the changes. Unless you think there
> > is independent value in the cleanup itself.
>
> Nay. At this point I am happy with the state of the test on HEAD. If
> there is a need for a refactoring piece in the future, we could always
> reconsider this piece at a later point.
> --
> Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-07-23 11:05:07 Re: Incorrect check in 037_except.pl?
Previous Message Christoph Berg 2026-07-23 10:44:29 Re: Allow pg_read_all_stats to see database size in \l+