| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal for Recover mode in pg_ctl (in 8.0) |
| Date: | 2004-11-07 08:53:15 |
| Message-ID: | 1099817595.6942.1770.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2004-11-07 at 00:54, Mark Kirkwood wrote:
> While this is nice, it will not help you if the restoration directory is
> different from your archive directory. That is : restore_command in
> recovery.conf fetches from somewhere other than where archive_command in
> postgresql.conf copied.
>
...hmmm, this doesn't look like an issue to me.
If the archive is protected when it's written, then it will be safe to
use later for restoration. The path to the archive may differ, but the
archive itself *needs* to be the same archive.
--
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-11-07 09:01:51 | Re: Proposal for Recover mode in pg_ctl (in 8.0) |
| Previous Message | Simon Riggs | 2004-11-07 08:35:42 | Re: Proposal for Recover mode in pg_ctl (in 8.0) |