From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WAL Restore process during recovery |
Date: | 2012-01-19 19:17:13 |
Message-ID: | CA+U5nMJ+Q-dk1CnTabOrj+ZTg3Xr9Lu=qjFKM-ajpgPv0nPqMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 17, 2012 at 6:52 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Mon, Jan 16, 2012 at 2:06 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> WALRestore process asynchronously executes restore_command while
>> recovery continues working.
>>
>> Overlaps downloading of next WAL file to reduce time delays in file
>> based archive recovery.
>>
>> Handles cases of file-only and streaming/file correctly.
>
> Though I've not reviewed the patch deeply yet, I observed the following
> two problems when I tested the patch.
>
> When I set up streaming replication + archive (i.e., restore_command is set)
> and started the standby, I got the following error:
>
> FATAL: all AuxiliaryProcs are in use
> LOG: walrestore process (PID 18839) exited with exit code 1
Fixed and better documented.
> When I started an archive recovery without setting restore_command,
> it successfully finished.
Not sure exactly what you mean, but I fixed a bug that might be
something you're seeing.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
walrestore_process.v2.patch | text/x-patch | 24.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-01-19 19:35:00 | Re: logging in high performance systems. |
Previous Message | Alvaro Herrera | 2012-01-19 19:15:12 | Re: Vacuum rate limit in KBps |