It sounds like PostgreSQL is set to recover from log shipping rather than by connecting as a replication user. Please double and triple check your recovery.conf and if that doesn't work, then post it here.
The approach you are taking is a valid approach though, and it means that the recovery will just wait for the next segment until it arrives creating the message you are seeing, but it must be transferred using whatever recovery command you have configured in the master's postgresql.conf.
how is it possible for the Slave to have more pg_xlog/ log files than the Master?
The whole point of archiving WAL on the master to some external location is to let the master then delete it to free space in its pg_xlog
, while replicas might still need it.
A replica can have more archives in pg_xlog
than the master, and older ones, if it's lagging behind the master due to failure to keep up with replay. However, with pg_standby
that shouldn't happen - the archive might contain more xlogs, but the replica should only be reading them on-demand.
It's hard to be specific, because you've given a broad description of the issue rather than actual directory listings, and haven't explained the exact steps you followed to set up the replica. Or shown the exact log file output from the replica. So the best I can do is "it sounds like the replica setup is broken somehw".
to resync the servers in warm standby mode: do I have to do pg_basebackup again (to essentially copy Master's /data
and /pg_xlog
directory) to the Slave?
Assuming that here /data
is the main datadir, containing global
, base
, pg_clog
, etc, and that pg_xlog
is the transaction logs from a different disk: Yes, that's right.
You must use the pg_basebackup
command, though, or follow the instructions in the manual for correct file system level copies using pg_start_backup()
and rsync/cp.
You also have to make sure you've stopped the replica first. Overwriting its datadir while it's running will make it quite upset.
Streaming replication vs warm standby
Hot vs warm standby is orthogonal to streaming vs log shipping replication.
What you're trying to do is use log shipping instead of streaming replication. It doesn't matter for this purpose if the replica is a hot standby or a warm standby, i.e. whether or not it's accepting queries.
Personally I recommend using both methods - use streaming, and fall back to log shipping if there's a problem with streaming. PostgreSQL does this automatically if both are configured.
Best Answer
Those words are often misunderstood and notions are often mixed up together because they arrived in the same version of PostgreSQL.
I hope this will help!