Postgres Pro
Downloads
Home   >   mailing lists

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

From Josh Berkus
Subject Re: Patch for fail-back without fresh backup
Date
Msg-id 52695B53.7050306@agliodbs.com
Whole thread Raw
In response to Re: Patch for fail-back without fresh backup  (Sawada Masahiko <sawada.mshk@gmail.com>)
Responses Re: Patch for fail-back without fresh backup  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
Tree view 
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?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: missing locking in at least INSERT INTO view WITH CHECK
Next
From: Heikki Linnakangas
Date:
Subject: Re: Patch for fail-back without fresh backup