From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Subject: Large number of partitions of a table
Date: Mon, 17 Jan 2022 02:44:19 +0000
Message-ID: <YeTYA63gEXNePfkv@admin.sibptus.ru> (raw)
Dear Colleagues,
Do you have success (or disaster) stories for having a large number of
partitions in a table (like maybe 10000) in a production database?
I've found a great article
https://www.depesz.com/2021/01/17/are-there-limits-to-partition-counts/
and basically it says 70000 partitions are OK but would like to hear
more opinions especially from production experience.
If a table itself has e.g. 50 indexes, partitioning it will create 10000
extra tables and 50*10000=500000 indexes, isn't it a heavy burden on the
system catalogs (pg_statistic etc). It may slow down ANALYZE or have
some other adverse effects.
Any comments welcome.
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet
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: vas@sibptus.ru, pgsql-admin@lists.postgresql.org
Subject: Re: Large number of partitions of a table
In-Reply-To: <YeTYA63gEXNePfkv@admin.sibptus.ru>
* 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