Re: Runtime pruning problem

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Yuzuko Hosoya <hosoya(dot)yuzuko(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Runtime pruning problem
Date: 2019-05-25 06:55:11
Message-ID: CAKJS1f_mw47rnotO4VvpmH42cVKAPn0bkTCzevugGPqeQrW6uQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 24 Apr 2019 at 11:42, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> I've added this to the July commitfest so that I don't forget about it.
>
> https://commitfest.postgresql.org/23/2102/

and an updated patch, rebased after the pgindent run.

Hopefully, this will make the CF bot happy again.

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

Attachment Content-Type Size
improve_runtime_pruning_explain_output_v2.patch application/octet-stream 38.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2019-05-25 07:53:35 Cleaning up and speeding up string functions
Previous Message Mark Kirkwood 2019-05-25 04:48:24 Re: Zedstore - compressed in-core columnar storage