Re: [HACKERS] Logical replication & corrupted pages recovery - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [HACKERS] Logical replication & corrupted pages recovery
Date
Msg-id CAMsr+YHrN8Agpg+ZsYRCA3HkhzQ3=jDAAHMn6eiwQJ4yJBAQuw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Logical replication & corrupted pages recovery  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
List pgsql-hackers


On 27 May 2017 01:03, "Aleksander Alekseev" <a.alekseev@postgrespro.ru> wrote:
Hi Konstantin,

> May be it is possible to somehow optimize it, by checking ranges of primary
> key values

It's possible. An optimization you are looking for is called Merkle
tree [1]. Particularly it's used in Riak [2].

[1] https://en.wikipedia.org/wiki/Merkle_tree
[2] http://docs.basho.com/riak/kv/2.2.3/learn/concepts/active-anti-entropy/

Personally I'd very much value a solid, standalone resynchronization function implemented in C using a PGconn. Even better if it could report differences and/or apply local changes.


pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] ALTER SUBSCRIPTION ..SET PUBLICATION refreshis not throwing error.
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Extra Vietnamese unaccent rules