Re: reorganizing partitioning code (was: Re: [HACKERS] path towardfaster partition pruning) - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: reorganizing partitioning code (was: Re: [HACKERS] path towardfaster partition pruning)
Date
Msg-id CAFjFpReeAPmo6U1UWsiD29bse8k--JMWgmJ9WB1Sf_8CTfy9PA@mail.gmail.com
Whole thread Raw
In response to reorganizing partitioning code (was: Re: [HACKERS] path toward fasterpartition pruning)  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On Tue, Feb 13, 2018 at 2:17 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
>
> Agree with the proposed reorganizing and adding a partcache.c, which I
> tried to do in the attached patch.
>
> * The new src/backend/utils/cache/partcache.c contains functions that
> initialize relcache's partitioning related fields.  Various partition
> bound comparison and search functions (and then some) that work off of the
> cached information are moved.

Are you moving partition bound comparison functions to partcache.c?
They will also used by optimizer, so may be leave them out of
partcache.c?

-- 
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company


pgsql-hackers by date:

Previous
From: Anthony Bykov
Date:
Subject: Re: Transform for pl/perl
Next
From: Alvaro Herrera
Date:
Subject: Re: [Sender Address Forgery]Re: [Sender Address Forgery]Re: [SenderAddress Forgery]Re: [HACKERS] path toward faster partition pruning