Re: max_locks_per_transaction and partitioned tables
| От | Tom Lane |
|---|---|
| Тема | Re: max_locks_per_transaction and partitioned tables |
| Дата | |
| Msg-id | 9791.1348088619@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | max_locks_per_transaction and partitioned tables (Michael Holt <MHolt@terapeak.com>) |
| Ответы |
Re: max_locks_per_transaction and partitioned tables
|
| Список | 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 по дате отправления: