Skip site navigation (1) Skip section navigation (2)

Re: Comment on max_locks_per_transaction

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-docs(at)postgreSQL(dot)org
Subject: Re: Comment on max_locks_per_transaction
Date: 2012-06-15 19:37:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
On 6/15/12 12:25 PM, Jeff Davis wrote:
> On Fri, 2012-06-15 at 11:05 -0700, Josh Berkus wrote:
>> The default, 64, has historically proven sufficient for most databases,
>> but you might need to raise this value if you have clients that touch
>> many different tables in a single transaction.  Databases with several
>> tables with many partitions each can require raising this setting.
> Is "partition" defined somewhere else in the docs?
> Maybe it should say something like: "Extensive use of table inheritance
> is the most common reason to increase this value from the default",
> assuming that's what you meant.

Hmmm.  I think we should also say "partitioning", as well as
"inheritance".  Maybe:

"Extensive use of table inheritance, such as for tables with many
partitions, may require raising this setting."


Josh Berkus
PostgreSQL Experts Inc.

In response to


pgsql-docs by date

Next:From: Jeff DavisDate: 2012-06-15 23:24:30
Subject: Re: Comment on max_locks_per_transaction
Previous:From: Jeff DavisDate: 2012-06-15 19:25:14
Subject: Re: Comment on max_locks_per_transaction

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group