From f24439dd2616b087a18c079f34bc633c85d29ffc Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Mon, 8 Apr 2024 14:23:57 +0100 Subject: [PATCH] Update product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx Co-authored-by: Nick Babadzhanian <33933459+pgnickb@users.noreply.github.com> --- product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx b/product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx index 2a472d9ad3d..ae00c9dd584 100644 --- a/product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx +++ b/product_docs/docs/pgd/5/consistency/column-level-conflicts.mdx @@ -36,7 +36,7 @@ Column-level conflict resolution requires the table to have `REPLICA IDENTITY FU ## Enabling and disabling column-level conflict resolution !!! Note Permissions Required -Column level conflict detection uses the `column_timestamp` type. This requires the user to have have at least the [bdr_application](security/pgd-predefined-roles/#bdr_application) role assigned to them. +Column level conflict detection uses the `column_timestamps` type. This requires the user to have have at least the [bdr_application](security/pgd-predefined-roles/#bdr_application) role assigned to them. !!! The [bdr.alter_table_conflict_detection()](conflicts#bdralter_table_conflict_detection) function manages column-level conflict resolution.