Re: max_locks_per_transaction and partitioned tables - Mailing list pgsql-admin

From Tom Lane
Subject Re: max_locks_per_transaction and partitioned tables
Date
Msg-id 9791.1348088619@sss.pgh.pa.us
Whole thread Raw
In response to max_locks_per_transaction and partitioned tables  (Michael Holt <MHolt@terapeak.com>)
Responses Re: max_locks_per_transaction and partitioned tables  (Michael Holt <MHolt@terapeak.com>)
List pgsql-admin
Michael Holt <MHolt@terapeak.com> writes:
> We've had a system in operation for a few years that makes use of a substantial amount of partitioning. The parent
tablenow has over 4,000 children tables. Within the last couple of days the server started giving "out of shared
memory"errors with the suggestion to increase the max_locks_per_transaction. 
> If the parent table is queried will it require a lock for each one of the child tables? I'm guessing it will.

Yup, it will.  I'm a bit astonished that you've gotten this far without
horrid performance problems.  The underlying mechanisms for inheritance
aren't really designed to scale past perhaps a hundred child tables.

            regards, tom lane


pgsql-admin by date:

Previous
From: Michael Holt
Date:
Subject: max_locks_per_transaction and partitioned tables
Next
From: Michael Holt
Date:
Subject: Re: max_locks_per_transaction and partitioned tables