Hi Stephen,
> On 13. Jul, 2020, at 17:47, Stephen Frost <sfrost@xxxxxxxxxxx> wrote:
>
> Sure, Patroni will handle the failover fine- but that's not what I was
> referring to. If the server crashes and you have no idea why or what
> happened, I would strongly recommend against using pg_rewind to rebuild
> it to be a replica as there's no validation happening- you might
> failover to it much later and, if you're lucky, discover quickly that
> some blocks had gotten corrupted or if you're unlucky not discover until
> much later that something was corrupted when the crash happened. Using
> initdb -k is good, but PG is only going to check the block when it goes
> to read it, which might not be until much later especially on a system
> that's been rebuilt as a replica.
I see your point, yet, I'm not sure how pgbackrest could protect us from such a situation.
> This seems like an independent question and I'm not really sure what is
> meant here by 'reinit it with Patroni'.
reinit basically deletes the replica database cluster and triggers a new full copy of the primary. You can either "patronictl reinit" or kill patroni, rm -r ${PGDATA}, and start patroni. This is basically the same.
> I agree that it'd be good to have -k on by default.
so, now, we're two. :-) Anyone else? ;-)
Cheers,
Paul
