Re: [PoC] Reducing planning time when tables have many partitions - Mailing list pgsql-hackers

From Andrey Lepikhov
Subject Re: [PoC] Reducing planning time when tables have many partitions
Date
Msg-id 807448d9-ccff-0fcc-e656-dc61f7f79052@postgrespro.ru
Whole thread Raw
In response to Re: [PoC] Reducing planning time when tables have many partitions  (Yuya Watari <watari.yuya@gmail.com>)
Responses Re: [PoC] Reducing planning time when tables have many partitions
List pgsql-hackers
On 2/11/2022 15:27, Yuya Watari wrote:
> Hello,
> 
> I noticed that the previous patch does not apply to the current HEAD.
> I attached the rebased version to this email.
> 
I'm still in review of your patch now. At most it seems ok, but are you 
really need both eq_sources and eq_derives lists now? As I see, 
everywhere access to these lists guides by eclass_source_indexes and 
eclass_derive_indexes correspondingly. Maybe to merge them?

-- 
regards,
Andrey Lepikhov
Postgres Professional




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: archive modules
Next
From: Tom Lane
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions