| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | David Rowley <drowley(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow run-time pruning on nested Append/MergeAppend nodes |
| Date: | 2020-11-02 06:29:51 |
| Message-ID: | 20201102062951.GB15770@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Hi David,
On Mon, Nov 02, 2020 at 12:49:52AM +0000, David Rowley wrote:
> Allow run-time pruning on nested Append/MergeAppend nodes
>
> Previously we only tagged on the required information to allow the
> executor to perform run-time partition pruning for Append/MergeAppend
> nodes belonging to base relations. It was thought that nested
> Append/MergeAppend nodes were just about always pulled up into the
> top-level Append/MergeAppend and that making the run-time pruning info for
> any sub Append/MergeAppend nodes was a waste of time. However, that was
> likely badly thought through.
fairywen is telling that some of the plans produced in these new tests
are not stable:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2020-11-02%2005%3A20%3A53
Thanks,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2020-11-02 06:44:23 | Re: pgsql: Allow run-time pruning on nested Append/MergeAppend nodes |
| Previous Message | Michael Paquier | 2020-11-02 06:17:48 | pgsql: Fix some grammar and typos in comments and docs |