max_locks_per_transaction and partitioned tables - Mailing list pgsql-admin

From Michael Holt
Subject max_locks_per_transaction and partitioned tables
Date
Msg-id E7907DC29186A94988A077445AFD1DC01497517B@EXCHANGEVIC.ad.terapeak.com
Whole thread Raw
Responses Re: max_locks_per_transaction and partitioned tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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

michael@terapeak.com

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

 

 

 

pgsql-admin by date:

Previous
From: Steve Crawford
Date:
Subject: Re: Postgres Cache usage
Next
From: Tom Lane
Date:
Subject: Re: max_locks_per_transaction and partitioned tables