From 39b42ecb059e24bb39a62d91fe57ab7b9ca5a2f5 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 30 Aug 2012 16:56:12 -0400 Subject: [PATCH] Document that max_locks_per_transaction might need to be increased for queries on parent tables, per suggestion from Josh Berkus. --- doc/src/sgml/config.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index d5fa94e2d4..ade9f7974d 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -5550,9 +5550,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' fit in the lock table. This is not the number of rows that can be locked; that value is unlimited. The default, 64, has historically proven sufficient, but you might need to - raise this value if you have clients that touch many different - tables in a single transaction. This parameter can only be set at - server start. + raise this value if you have queries that touch many different + tables in a single transaction, e.g. query of a parent table with + many children. This parameter can only be set at server start.