From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Venkata B Nagothi <nag1010(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch proposal |
Date: | 2016-11-09 18:29:13 |
Message-ID: | CAJGNTePJRhZj00-u4cE90otiJNnn9buXrcrs440+W7H-ihaD1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16 August 2016 at 09:06, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Greetings,
>
> * Venkata B Nagothi (nag1010(at)gmail(dot)com) wrote:
>> The above said parameters can be configured to pause, shutdown or prevent
>> promotion only after reaching the recovery target point.
>> To clarify, I am referring to a scenario where recovery target point is not
>> reached at all ( i mean, half-complete or in-complete recovery) and there
>> are lots of WALs still pending to be replayed - in this situation,
>
> PG doesn't know that there are still WALs to be replayed.
>
>> PostgreSQL just completes the archive recovery until the end of the last
>> available WAL (WAL file "00000001000000000000001E" in my case) and
>> starts-up the cluster by generating an error message (saying
>> "00000001000000000000001F" not found).
>
> That's not a PG error, that's an error from cp. From PG's perspective,
> your restore command has said that all of the WAL has been replayed.
>
> If that's not what you want then change your restore command to return
> an exit code > 125, which tells PG that it's unable to restore that WAL
> segment.
>
Ah! Is this documented somewhere?
if we expect people to use correct exit codes we should document them, no?
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-11-09 18:29:32 | Re: Unlogged tables cleanup |
Previous Message | Tom Lane | 2016-11-09 18:29:11 | Re: IPv6 link-local addresses and init data type |