From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Holt <MHolt@terapeak.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: max_locks_per_transaction and partitioned tables
Date: Wed, 19 Sep 2012 17:03:39 -0400
Message-ID: <9791.1348088619@sss.pgh.pa.us> (raw)
In-Reply-To: <E7907DC29186A94988A077445AFD1DC01497517B@EXCHANGEVIC.ad.terapeak.com>
References: <E7907DC29186A94988A077445AFD1DC01497517B@EXCHANGEVIC.ad.terapeak.com>
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 table now 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, MHolt@terapeak.com
Subject: Re: max_locks_per_transaction and partitioned tables
In-Reply-To: <9791.1348088619@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox