| From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pitr replica dies on startup |
| Date: | 2007-09-01 01:24:08 |
| Message-ID: | Pine.LNX.4.64.0708311822070.11463@discord.home.frostconsultingllc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 31 Aug 2007, Tom Lane wrote:
> Jeff Frost <jeff(at)frostconsultingllc(dot)com> writes:
>> It seems like everything is happy, except it seems to ask for the 4F
>> log file more than once.
>
> IIRC that's standard procedure. Is there a reason your recovery_command
> can't support it?
Really? If that's the case, then no, this particular recovery command
archives the WAL files off into an archive directory after they've been
successfully copied. So, the second time postgres asks for it, it won't be
available.
Thanks for the idea Tom, I'll update the script to look in the archive
directory if the file is unavailable in the backup directory.
Why does it request it twice?
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-01 01:45:10 | Re: pitr replica dies on startup |
| Previous Message | Tom Lane | 2007-08-31 23:19:33 | Re: pitr replica dies on startup |