Skip site navigation (1) Skip section navigation (2)

max_locks_per_transaction and partitioned tables

From: Michael Holt <MHolt(at)terapeak(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: max_locks_per_transaction and partitioned tables
Date: 2012-09-19 18:25:01
Message-ID: E7907DC29186A94988A077445AFD1DC014975161@EXCHANGEVIC.ad.terapeak.com (view raw or flat)
Thread:
Lists: pgsql-admin
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.
--
Michael Holt   |   Manager, Data Services   |   Linkedin Profile<http://ca.linkedin.com/pub/michael-holt/48/a21/5ab>


michael(at)terapeak(dot)com<mailto:michael(at)terapeak(dot)com>

102-3962 Borden Street, Victoria, B.C., Canada V8P 3H8





pgsql-admin by date

Next:From: Michael HoltDate: 2012-09-19 18:28:16
Subject: max_locks_per_transaction and partitioned tables
Previous:From: Steve CrawfordDate: 2012-09-19 17:38:03
Subject: Re: Postgres Cache usage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group