| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | shveta malik <shveta(dot)malik(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Conflict Detection and Resolution |
| Date: | 2024-06-13 12:45:50 |
| Message-ID: | ad4ab5bd-603a-4ee2-9514-e79c0c391ed7@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-06-13 13:30:33 | Re: Conflict Detection and Resolution |
| Previous Message | Masahiko Sawada | 2024-06-13 12:44:05 | Re: Logical Replication of sequences |