| From: | Victor Sudakov <vas(at)sibptus(dot)ru> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Large number of partitions of a table |
| Date: | 2022-01-17 02:44:19 |
| Message-ID: | YeTYA63gEXNePfkv@admin.sibptus.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(at)fidonet
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-17 04:27:48 | Re: Large number of partitions of a table |
| Previous Message | Holger Jakobs | 2022-01-15 22:15:37 | Re: pgAadmin 4 internal vs external browser macOS |