Message-ID: <4FDB8EDF.2080904@agliodbs.com>
Date: Fri, 15 Jun 2012 12:37:03 -0700
From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL Experts Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Jeff Davis <pgsql@j-davis.com>
CC: pgsql-docs@postgreSQL.org
Subject: Re: Comment on max_locks_per_transaction
References: <4FDB796A.7080803@agliodbs.com>
	<1339788314.16772.3.camel@sussancws0025>
In-Reply-To: <1339788314.16772.3.camel@sussancws0025>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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."

Works?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com