Folks,
Way it is now:
===
max_locks_per_transaction (integer)
The shared lock table tracks locks on max_locks_per_transaction *
(max_connections + max_prepared_transactions) objects (e.g., tables);
hence, no more than this many distinct objects can be locked at any one
time. Thi
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 partiti
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. Datab
On Fri, 2012-06-15 at 12:37 -0700, Josh Berkus wrote:
> 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."
http://www.postgresql.org/docs/9.2/s
