Re: Out of shared memory (locks per process) using table-inheritance style partitioning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John Prevost" <j(dot)prevost(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Out of shared memory (locks per process) using table-inheritance style partitioning
Date: 2007-08-30 18:43:06
Message-ID: 6726.1188499386@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"John Prevost" <j(dot)prevost(at)gmail(dot)com> writes:
> So, what's the problem? Well=97I have twelve tables that are
> partitioned by hour. There are 24 hours in a day, there are seven
> days in a week, and... you may see where I'm going here. PostgreSQL
> gets a lock on each individual table queried (in this case, every
> single partition) and it doesn't take very long at all for the maximum
> number of locks (~2240 by default) to be taken out, particularly when
> data is being aggregated across the twelve different partitioned
> tables.

So what's the problem? Increase max_locks_per_transaction. The reason
we have that as a tunable is mainly to support systems with very large
numbers of tables.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ned Lilly 2007-08-30 18:45:42 Re: PostgreSQL Conference Fall 2007
Previous Message Madison Kelly 2007-08-30 18:35:21 Solved! Was: Re: Select question