Re: Run-time pruning for ModifyTable - Mailing list pgsql-hackers

From David Rowley
Subject Re: Run-time pruning for ModifyTable
Date
Msg-id CAApHDvriM918qSynhCEkb8a-FZXiubWcmmKhJZDYSrzs9wYueQ@mail.gmail.com
Whole thread Raw
In response to Re: Run-time pruning for ModifyTable  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Run-time pruning for ModifyTable  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On Wed, 25 Mar 2020 at 13:00, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > I had a closer look at this today and the code I have in
> > inheritance_planner() is certainly not right.
>
> Although I didn't get around to it for v13, there's still a plan on the
> table for inheritance_planner() to get nuked from orbit [1].
>
> Maybe this improvement should be put on hold till that's done?

Possibly. I'm not really wedded to the idea of getting it in. However,
it would really only be the inheritance planner part that would need
to be changed later. I don't think any of the other code would need to
be adjusted.

Amit shared his thoughts in [1].  If you'd rather I held off, then I will.

David

[1] https://www.postgresql.org/message-id/CA%2BHiwqGhD7ieKsv5%2BGkmHgs-XhP2DoUhtESVb3MU-4j14%3DG6LA%40mail.gmail.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Include sequence relation support in logical replication
Next
From: James Coleman
Date:
Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort)