Re: Some incorrect comments and out-dated README from run-time pruning - Mailing list pgsql-hackers

From David Rowley
Subject Re: Some incorrect comments and out-dated README from run-time pruning
Date
Msg-id CAKJS1f-JvCH6X1Corc0=4uVFw-G1+6_cz9MsJ5yvwO-=HbRJxQ@mail.gmail.com
Whole thread Raw
In response to Some incorrect comments and out-dated README from run-time pruning  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
On 28 September 2018 at 09:20, David Rowley
<david.rowley@2ndquadrant.com> wrote:
> I've noticed that the comments above the PartitionedRelPruneInfo
> struct incorrectly document how subplan_map and subpart_map are
> indexed. This seems to have snuck in on 4e232364033.
>
> Also, while reading the executor README file, I noticed that we
> mentioned that executor nodes are created one for one for each
> corresponding plan node. This is no longer completely true. Some
> Append / MergeAppend subnodes may be skipped when performing run-time
> pruning at executor startup. I thought it might be best to mention
> that in the README.
>
> Patch attached.

Added to the November 'fest.

https://commitfest.postgresql.org/20/1812/

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


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgbench - test whether a variable exists
Next
From: Tom Lane
Date:
Subject: Re: executor relation handling