From: Victor Sudakov <vas@sibptus.ru>
To: pgsql-admin@lists.postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Large number of partitions of a table
Date: Mon, 17 Jan 2022 05:38:15 +0000
Message-ID: <YeUAx56Juri43xGY@admin.sibptus.ru> (raw)
In-Reply-To: <3919502.1642393668@sss.pgh.pa.us>
References: <YeTYA63gEXNePfkv@admin.sibptus.ru>
<3919502.1642393668@sss.pgh.pa.us>
Tom Lane wrote:
[dd]
> The specific point that depesz was responding to in that blog
> was the 64K-ish limit on rangetable entries in a query. That is
> a thing, as he could have shown by using queries that weren't
> amenable to plan-time pruning. (It's also an ex-thing, having
> been fixed for v15 [1]; but that doesn't help you today.)
> Now, if you use no queries that can't be pruned to a few
> partitions, then it's academic for you.
The table will be partitioned `BY LIST (customer_id)` which is a unique
index. All queries will be using this index so no query should ever
have to use more than 1 partition.
This means basically I'm OK?
--
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, tgl@sss.pgh.pa.us
Subject: Re: Large number of partitions of a table
In-Reply-To: <YeUAx56Juri43xGY@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