On Mon, Mar 18, 2013 at 2:08 PM, Niels Kristian Schjødt
<nielskristian@autouncle.com> wrote:
> Okay, thanks. It' seems you were right! Now I have fixed the issue (it was an ssh key).
> So I started a:
> SELECT pg_start_backup('backup', true);
>
> And when done, I executed a:
> sudo -u postgres rsync -av --exclude postmaster.pid --exclude pg_xlog /var/lib/postgresql/9.2/main/
postgres@192.168.0.2:/var/lib/postgresql/9.2/main/
>
> Then I tried to finish off the backup by doing a:
> SELECT pg_stop_backup();
>
> But It keeps on telling me:
> WARNING: pg_stop_backup still waiting for all required WAL segments to be archived (480 seconds elapsed)
> HINT: Check that your archive_command is executing properly. pg_stop_backup can be canceled safely, but the
databasebackup will not be usable without all the WAL segments.
>
> And I could see in the log that it's some kind of permission issue. So I canceled it, and started the streaming
replicationon my slave, and it seems to work fine. However the pg_xlog dir on the master is still HUGE 153G - so how
canI get this mess sorted, and cleaned up that directory?
Once you have your archive_command working, it will transfer all your
xlog to the archive. Once it is, the xlog directory should
automatically clean up fairly quickly.
If you still have a permissions problem with the archive, you
obviously need to fix that first.
If you don't care about your archive you could set your
archive_command to e.g. /bin/true, and that will make it pretend it
has archived the files, and should clean it up quicker. But that will
mean you have no valid archive and thus no valid backups, until you
start over froma new base.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
