Re: pg_resetwal: refuse to run when backup_label exists

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

Hi Joao,

Thanks for testing v3.

> A backup_label looks like that second kind to me, so I'd keep v3
> as is.

Agreed, I will leave v3 as it is.

I see the CF entry is now Waiting on Author. Is there something you
want me to change in v3? If not, I think it can go back to Needs
review, or Ready for Committer if you think it is ready.

Thanks,
Shihao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-05 15:01:05 Re: doc: Document Linux cgroup memory limits
Previous Message Mark Dilger 2026-10-05 14:41:28 Re: amcheck: detect corruption from the recent snapshot-export bug