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:28:16
Message-ID: E7907DC29186A94988A077445AFD1DC01497517B@EXCHANGEVIC.ad.terapeak.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2012-09-19 21:03:39 Re: max_locks_per_transaction and partitioned tables
Previous Message Michael Holt 2012-09-19 18:25:01 max_locks_per_transaction and partitioned tables