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: | 4FDB8EDF.2080904@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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."
Works?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2012-06-15 23:24:30 | Re: Comment on max_locks_per_transaction |
Previous Message | Jeff Davis | 2012-06-15 19:25:14 | Re: Comment on max_locks_per_transaction |