From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Mark Kirkwood <markir(at)coretech(dot)co(dot)nz>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal for Recover mode in pg_ctl (in 8.0) |
Date: | 2004-11-07 19:13:57 |
Message-ID: | 23248.1099854837@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Sat, 2004-11-06 at 23:29, Tom Lane wrote:
>> A possibly more reliable interlock would involve having the postmaster
>> probe during normal startup to see if there is already an archived WAL
>> segment for what it thinks is the current segment.
> Yes, checking the archive is the safe way, but we don't know how to do
> that unless restore_command has been successfully read in (currently
> from recovery.conf). Putting it in postgresql.conf is the wrong place,
Agreed; we left it out of postgresql.conf for good reasons. I was
thinking in terms of adding a third command string, perhaps like
test_archive_file = 'test -f /mnt/server/archive/%f'
But it's probably best just to tell people to write their
archive_commands in a non-overwrite style.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-11-07 19:28:20 | Re: pg_arch.c call to sleep() |
Previous Message | Tom Lane | 2004-11-07 19:01:45 | Re: Documentation on PITR still scarce |