Skip to content

Update conflicts.mdx #6853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions product_docs/docs/pgd/4/bdr/conflicts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -852,12 +852,10 @@ conflict detection independent of the nodes' system clock.
Row version conflict detection requires that you enable three things. If any of these
steps aren't performed correctly then [origin conflict detection](#origin-conflict-detection) is used.

1. `check_full_tuple` must be enabled for the BDR node group.

2. `REPLICA IDENTITY FULL` must be enabled on all tables that use
1. `REPLICA IDENTITY FULL` must be enabled on all tables that use
row version conflict detection.

3. Row Version Tracking must be enabled on the table by using
2. Row Version Tracking must be enabled on the table by using
`bdr.alter_table_conflict_detection`. This function adds a column
(with a name you specify) and an `UPDATE` trigger that manages the new
column value. The column is created as `INTEGER` type.
Expand Down