From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Pause at end of recovery |
Date: | 2012-01-26 17:42:26 |
Message-ID: | CAHGQGwEBbekM+2voi64kuBcSX36Gj2BRLCRx8+1x1LmhYg7M=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 27, 2012 at 12:50 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> One idea; starting archive recovery with standby_mode=on meets your needs?
>
> I haven't tested, but probably, yes. But in that case, why do we need
> the pause_at_recovery_target *at all*? It's basically overloaded
> functionality already, but I figured it was set up that way to keep
> replication and recovery a bit separated?
AFAIK, when standby_mode = on, archive recovery pauses only at end of WAL files.
When recovery target is specified and archive recovery reaches the
target, it doesn't
pause. OTOH, when pause_at_recovery_target is set, archive recovery pauses only
at the target but not end of WAL files. Neither can cover all the usecases. So
pause_at_recovery_target was implemented.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-01-26 17:47:55 | Re: Different error messages executing CREATE TABLE or ALTER TABLE to create a column "xmin" |
Previous Message | Dimitri Fontaine | 2012-01-26 17:40:06 | Re: Inline Extension |