From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Large number of partitions of a table
Date: Mon, 17 Jan 2022 08:41:34 -0600
Message-ID: <671340a5-1960-e5dc-1d09-4b7f36cda2c8@gmail.com> (raw)
In-Reply-To: <YeUAx56Juri43xGY@admin.sibptus.ru>
References: <YeTYA63gEXNePfkv@admin.sibptus.ru>
<3919502.1642393668@sss.pgh.pa.us>
<YeUAx56Juri43xGY@admin.sibptus.ru>
On 1/16/22 11:38 PM, Victor Sudakov wrote:
> 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
Good.
> so no query should ever have to use more than 1 partition.
I find it hard to believe that you'll *never* run a report against more
customers than are in a single partition.
>
> This means basically I'm OK?
>
--
Angular momentum makes the world go 'round.
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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Large number of partitions of a table
In-Reply-To: <671340a5-1960-e5dc-1d09-4b7f36cda2c8@gmail.com>
* 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