Hello
a max_locks_per_transaction is twice times in postgresql.conf.sample
Attached simple bugfix
Regards
Pavel
commit 89ee480408e63fc39fb6b7a23871c4f46438b7a2
Author: Pavel Stehule <pavel.steh...@gooddata.com>
Date: Thu Jan 29 12:21:07 2015 +0100
remove twice max_locks_per_transaction variable in postgresql.conf.sample
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample
index b053659..5f1a0da 100644
--- a/src/backend/utils/misc/postgresql.conf.sample
+++ b/src/backend/utils/misc/postgresql.conf.sample
@@ -562,8 +562,6 @@
#------------------------------------------------------------------------------
#deadlock_timeout = 1s
-#max_locks_per_transaction = 64 # min 10
- # (change requires restart)
# Note: Each lock table slot uses ~270 bytes of shared memory, and there are
# max_locks_per_transaction * (max_connections + max_prepared_transactions)
# lock table slots.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
