So last night our PG Slave ran out of space after a lot of reconfiguring of disk space, new drives etc its now reporting the following error:
FATAL: could not receive data from WAL stream: FATAL: requested WAL segment 00000001000018F70000008A has already been removed
From the reading around this I've done, it appears that the only solution is to re-sync the slave with pg_start_backup() et al. Based on this, I have a few questions.
- Is there a better way of fixing the slave that I've simply missed or overlooked?
- Do I need to clear out the WAL files on the slave and/or master prior or during the backup?
- Does pg_start_backup lock the database during this time?
As requested, the log file can be found: http://pastebin.com/9F8vJh6R, have removed the rest of the file as its just 5 hours of the same repeated error
Many thanks
pg_start_backup()
is not supposed to lock the DB, except when you passfast = TRUE
to it - this latter will cause a slowdown of any concurrently executing queries. See postgresql.org/docs/9.4/static/…