Re: Runtime partition pruning for MergeAppend

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Runtime partition pruning for MergeAppend
Date: 2018-07-19 12:15:05
Message-ID: CAKJS1f9LtgRKOHfhL=T-SY10CBvBZy1Awy3d27Lcer_4Rua_3Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19 July 2018 at 23:22, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> for getting custom plan, you don't need execute 5x now. Just use
> plan_cache_mode GUC.

Yeah. It's good to see that patch in. I wonder if we should go and
change those tests to get rid of the 5x EXECUTEs before the actual
test.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-07-19 12:28:05 Re: GiST VACUUM
Previous Message David Rowley 2018-07-19 12:13:46 Re: Runtime partition pruning for MergeAppend