Re: pg_resetwal: refuse to run when backup_label exists

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Joao Detomini <joao(dot)detomini(at)enterprisedb(dot)com>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, David Steele <david(at)pgbackrest(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_resetwal: refuse to run when backup_label exists
Date: 2026-10-05 22:32:19
Message-ID: asQlc0x7FPjAWdvJ@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 05, 2026 at 12:04:14PM -0300, Joao Detomini wrote:
> Nothing to change from my side, v3 looks fine to me. I'll put it
> back to Needs review for now, since Michael hasn't said whether he's
> ok with -f not overriding the check.

I'm maybe just not seeing the value of the patch, then, that's all, so
I doubt that my opinion has any value.

Please note that the community mailing lists follow the following
style in terms of message posting:
https://en.wikipedia.org/wiki/Posting_style#Bottom-posting
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mihail Nikalayeu 2026-10-05 22:35:00 Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates
Previous Message Michael Paquier 2026-10-05 22:27:24 Re: WAL segment file descriptor leak on read errors can PANIC the server