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

From Tom Lane
Subject Re: Out of shared memory (locks per process) using table-inheritance style partitioning
Date
Msg-id 6726.1188499386@sss.pgh.pa.us
Whole thread Raw
In response to Out of shared memory (locks per process) using table-inheritance style partitioning  ("John Prevost" <j.prevost@gmail.com>)
Responses Re: Out of shared memory (locks per process) using table-inheritance style partitioning
List pgsql-general
"John Prevost" <j.prevost@gmail.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

pgsql-general by date:

Previous
From: Madison Kelly
Date:
Subject: Solved! Was: Re: Select question
Next
From: Andrew Sullivan
Date:
Subject: Re: Reliable and fast money transaction design