Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, Chapman Flack <chap(at)anastigmatix(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date: 2022-03-01 16:39:55
Message-ID: 20220301163955.GU10577@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greetings,

* Nathan Bossart (nathandbossart(at)gmail(dot)com) wrote:
> On Tue, Mar 01, 2022 at 08:44:51AM -0600, David Steele wrote:
> > Personally, I am in favor of removing it. We change/rename
> > functions/tables/views when we need to, and this happens in almost every
> > release.
> >
> > What we need to do is make sure that an older installation won't silently
> > work in a broken way, i.e. if we remove the exclusive flag somebody
> > expecting the pre-9.6 behavior might not receive an error and think
> > everything is OK. That would not be good.
> >
> > One option might be to rename the functions. Something like
> > pg_backup_start/stop.
>
> I'm fine with this approach.

+1.

Thanks,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Heiss 2022-03-01 16:40:45 Re: [PATCH] Add reloption for views to enable RLS
Previous Message Justin Pryzby 2022-03-01 16:37:58 Re: Commitfest 2022-03 Patch Triage Part 1a.i