From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Rene Romero Benavides <rene(dot)romero(dot)b(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: restore_command ignored in recovery.conf on standby |
Date: | 2014-04-14 02:58:55 |
Message-ID: | 20140414025855.GT2556@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Rene Romero Benavides (rene(dot)romero(dot)b(at)gmail(dot)com) wrote:
> Yep, I checked:
>
> [postgres(at)uxmal standby_node]$ /bin/tar -xzf
> /db/wal_archives/00000001000001ED000000FB.tar.gz -C
> /db/standby_node/pg_xlog/
> [postgres(at)uxmal standby_node]$ echo $?
> 0
Err, sure, but that isn't actually what is being passed via %p. %p will
be something like 'pg_xlog/RECOVERY_WAL', as I said, which *won't* work
for your tar command, eg:
sfrost(at)tamriel:/home/sfrost> tar -xzf zz.tar.gz -C zz/zz
tar: zz/zz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
sfrost(at)tamriel:/home/sfrost> echo $?
2
> [postgres(at)uxmal standby_node]$ ls /db/standby_node/pg_xlog/ | grep
> 00000001000001ED000000FB
> 00000001000001ED000000FB
Noooo, PG tells you via %p the *specific* filename to use, do not just
overwrite files in pg_xlog willy-nilly with a tar command.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Rene Romero Benavides | 2014-04-14 03:13:17 | Re: restore_command ignored in recovery.conf on standby |
Previous Message | Rene Romero Benavides | 2014-04-14 02:52:10 | Re: restore_command ignored in recovery.conf on standby |