Closed serprex closed 20 hours ago
when primary key updated row becomes duplicate because old version isn't marked outdated, generate deletion records behind updates
disabled by default due to perf impact, can be enabled with PEERDB_CLICKHOUSE_ENABLE_PRIMARY_UPDATE
PEERDB_CLICKHOUSE_ENABLE_PRIMARY_UPDATE
if custom ordering is on a non replica identity column then row data may be missing, causing this to fail to prevent duplication
Given updating primary keys is quite rare (difficult to do with pg if you use foreign keys) it may be better to have this disabled by default so that updates aren't generating twice as many rows on destination
when primary key updated row becomes duplicate because old version isn't marked outdated, generate deletion records behind updates
disabled by default due to perf impact, can be enabled with
PEERDB_CLICKHOUSE_ENABLE_PRIMARY_UPDATE
if custom ordering is on a non replica identity column then row data may be missing, causing this to fail to prevent duplication