| From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
|---|---|
| To: | Ildar Musin <i(dot)musin(at)postgrespro(dot)ru> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: partition pruning by secondary attributes |
| Date: | 2018-02-09 06:03:46 |
| Message-ID: | CAFjFpRdPzR=jOqJ6J2dLthyqeytQC_vreStzobhXkBGrUZam5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 8, 2018 at 4:51 PM, Ildar Musin <i(dot)musin(at)postgrespro(dot)ru> wrote:
>
> The idea is to store min and max values of secondary attributes (like
> 'id' in the example above) for each partition somewhere in catalog and
> use it for partition pruning along with partitioning key.
Every insertion and update of secondary attribute will touch catalog
and update if required. That will increase the contention on catalog.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2018-02-09 06:05:38 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |
| Previous Message | Amit Langote | 2018-02-09 05:56:28 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |