Re: Large number of partitions of a table - Mailing list pgsql-admin

From Victor Sudakov
Subject Re: Large number of partitions of a table
Date
Msg-id YeUAx56Juri43xGY@admin.sibptus.ru
Whole thread Raw
In response to Re: Large number of partitions of a table  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Large number of partitions of a table  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-admin
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



pgsql-admin by date:

Previous
From: Victor Sudakov
Date:
Subject: Re: Large number of partitions of a table
Next
From: Halat-Pruvot Sylvie
Date:
Subject: RE: postgresql wait event and high active connection