Skip site navigation (1) Skip section navigation (2)

Re: BUG #3110: Online Backup introduces Duplicate OIDs

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Randy Isbell (jisbell)" <jisbell(at)cisco(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3110: Online Backup introduces Duplicate OIDs
Date: 2008-06-05 15:31:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, 2008-06-05 at 10:59 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > I would like to introduce a WARNING message into recovery to show that a
> > backup_label was expected, yet was not present. This is normal in some
> > use cases of recovery, but we need to be able to tell those situations
> > apart. Any objections?
> Given that the case would sometimes be expected, I think a warning would
> just add confusion.  If we could distinguish the cases and make it a
> hard ERROR to be lacking the label when it's needed, then maybe, but I'm
> not sure how.

OK, understood.

How about we do this:

* Add some more docs

* Put a specific warning about the need for a backup_label file into the
next release notes for 8.x.x releases. "Important change to docs for

* In the release note comments, add that in a future release we will add
a parameter to recovery.conf "require_backup_label" which defaults to

* Repeat this warning in the next release notes also

* On the one after that we actually make the change. Once we add this,
if the backup_label is missing then we throw an ERROR.

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2008-06-05 15:39:14
Subject: Re: BUG #3110: Online Backup introduces Duplicate OIDs
Previous:From: Tom LaneDate: 2008-06-05 14:59:29
Subject: Re: BUG #3110: Online Backup introduces Duplicate OIDs

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group