Re: Patch for fail-back without fresh backup - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Patch for fail-back without fresh backup
Date
Msg-id 5269630B.1060107@vmware.com
Whole thread Raw
In response to Re: Patch for fail-back without fresh backup  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 24.10.2013 20:39, Josh Berkus wrote:
> On 10/24/2013 04:15 AM, Pavan Deolasee wrote:
>> If we do what you are suggesting, it seems like a single line patch to me.
>> In XLogSaveBufferForHint(), we probably need to look at this additional GUC
>> to decide whether or not to backup the block.
>
> Wait, what?  Why are we having an additional GUC?
>
> I'm opposed to the idea of having a GUC to enable failback.  When would
> anyone using replication ever want to disable that?

For example, if you're not replicating for high availability purposes, 
but to keep a reporting standby up-to-date.

- Heikki



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Patch for fail-back without fresh backup
Next
From: Peter Eisentraut
Date:
Subject: Re: Reasons not to like asprintf