Re: Run-time pruning for ModifyTable

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Run-time pruning for ModifyTable
Date: 2019-07-03 07:34:03
Message-ID: CAKJS1f9j8r6ap963qrgPdCxkTtj2Kr=tmNm_w9eZ1+Nyf=ksAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 3 Jul 2019 at 17:27, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> A cursory look at the patch suggests that most of its changes will be
> for nothing if [1] materializes. What do you think about that?

Yeah, I had this in mind when writing the patch, but kept going
anyway. I think it's only really a small patch of this patch that
would get wiped out with that change. Just the planner.c stuff.
Everything else is still required, as far as I understand.

> [1] https://www.postgresql.org/message-id/357.1550612935%40sss.pgh.pa.us

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-07-03 07:34:54 Re: Custom table AMs need to include heapam.h because of BulkInsertState
Previous Message Oleksandr Shulgin 2019-07-03 07:29:32 Re: POC: converting Lists into arrays