Hopefully, you set keep_wal_segments high enough that nothing has "expired" from the master, if this is the case and if you set up the slave so it can see those WAL segments, then your job is done. Just start the slave up and it will process those transactions from the WAL segments that weren't part of the pg_basebackup.
If, however, some of those WAL segments have disappeared off the master server, then you get to perform this exercise all over again, i.e., a new pg_basebackup.
--
Jay
On Wed, Feb 17, 2016 at 9:02 AM, Dave Johansen <davejohansen@xxxxxxxxx> wrote:
On Sat, Feb 6, 2016 at 6:38 PM, John Scalia <jayknowsunix@xxxxxxxxx> wrote:If you specify -X f or more likely -X s, that will cause pg_basebackup to include the WAL files that were written after you started the operation. Since you're setting up a replica, use the -X s option as that's for streaming.I ran pg_basebackup with -X s and it finished in the middle of the night last night. I would now like to make the switch, but what's the best way to copy over the records that have been inserted since the backup stopped?
