Re: Conflict Detection and Resolution
От | Peter Eisentraut |
---|---|
Тема | Re: Conflict Detection and Resolution |
Дата | |
Msg-id | ad4ab5bd-603a-4ee2-9514-e79c0c391ed7@eisentraut.org обсуждение исходный текст |
Ответ на | Conflict Detection and Resolution (shveta malik <shveta.malik@gmail.com>) |
Ответы |
RE: Conflict Detection and Resolution
|
Список | pgsql-hackers |
On 23.05.24 08:36, shveta malik wrote: > Conflict Resolution > ---------------- > a) latest_timestamp_wins: The change with later commit timestamp wins. > b) earliest_timestamp_wins: The change with earlier commit timestamp wins. > c) apply: Always apply the remote change. > d) skip: Remote change is skipped. > e) error: Error out on conflict. Replication is stopped, manual > action is needed. You might be aware of pglogical, which has similar conflict resolution modes, but they appear to be spelled a bit different. It might be worth reviewing this, so that we don't unnecessarily introduce differences. https://github.com/2ndquadrant/pglogical?tab=readme-ov-file#conflicts There might also be other inspiration to be found related to this in pglogical documentation or code.
В списке pgsql-hackers по дате отправления: