On 11/19/15 2:13 AM, Michael Paquier wrote:
> On Thu, Nov 19, 2015 at 7:10 AM, Stephen Frost wrote:
>> * Michael Paquier (michael.paquier@gmail.com) wrote:
>>> It seems weird to not have a dedicated role for pg_switch_xlog.
>>
>> I didn't add a pg_switch_xlog default role in this patch series, but
>> would be happy to do so if that's the consensus. It's quite easy to do.
>
> Agreed. I am not actually getting why that's part of the backup
> actually. That would be more related to archiving, both being
> unrelated concepts. But at this point I guess that's mainly a
> philosophical split.
I wouldn't say that backup and archiving are unrelated since backups
aren't valid without the proper set of WAL segments.
When configuring archiving/backup I use pg_switch_xlog() to verify that
WAL segments are getting to the archive.
I also use pg_switch_xlog() after pg_create_restore_point() to force the
WAL segment containing the restore point record to the archive.
Otherwise it might not be possible (or at least not easy) to recover to
the restore point in case of a problem. The required WAL segment is
likely to get pushed to the archive before it is needed but I would
rather not bet on that.
--
-David
david@pgmasters.net
