From 95171d32dfe5db3aaec6f21770984cf0ff19688f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Fri, 20 Sep 2024 14:10:30 +0100 Subject: [PATCH] Update product_docs/docs/pgd/5/reference/pgd-settings.mdx Co-authored-by: Florin Irion --- product_docs/docs/pgd/5/reference/pgd-settings.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/reference/pgd-settings.mdx b/product_docs/docs/pgd/5/reference/pgd-settings.mdx index e4614fd4a97..08633f62198 100644 --- a/product_docs/docs/pgd/5/reference/pgd-settings.mdx +++ b/product_docs/docs/pgd/5/reference/pgd-settings.mdx @@ -156,7 +156,7 @@ lock (default is 10 minutes). A value of zero disables this timeout. ### `bdr.lock_table_locking` -Defaults to `off`. When enabled PGD treats every lock as a global DML lock. This makes the entire cluster wait for the lock to be released. This setting is useful for debugging and testing purposes. +Defaults to off. This configuration option sets locking behavior for LOCK TABLE Statement; when enabled, LOCK TABLE statement will also take a global DML lock on the cluster, blocking other locking statements. | Value | Description | | --- | --- |