Minor comment edits in nodeGather.c

Started by Amit Langoteover 10 years ago6 messageshackers
Jump to latest
#1Amit Langote
Langote_Amit_f8@lab.ntt.co.jp

While going through nodeGather.c, I noticed portions of the file header
comment that may have been obsoleted by recent revisions of the relevant
parellelism code. For example, there is a reference to PartialSeqScan node
which did not make it into the tree. Attached fixes it. Also, wondering if
the semantics of Gather node is that of Scan or more generic Plan? That is
to ask whether the following edit makes sense:

  * nodeGather.c
- *	  Support routines for scanning a plan via multiple workers.
+ *	  Support routines for getting the result from a plan via multiple
+ *	  workers.
  *

Thanks,
Amit

Attachments:

nodegather-comment-fix.patchtext/x-diff; name=nodegather-comment-fix.patchDownload+4-2
#2Robert Haas
robertmhaas@gmail.com
In reply to: Amit Langote (#1)
Re: Minor comment edits in nodeGather.c

On Tue, Nov 24, 2015 at 1:06 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:

While going through nodeGather.c, I noticed portions of the file header
comment that may have been obsoleted by recent revisions of the relevant
parellelism code. For example, there is a reference to PartialSeqScan node
which did not make it into the tree. Attached fixes it. Also, wondering if
the semantics of Gather node is that of Scan or more generic Plan? That is
to ask whether the following edit makes sense:

* nodeGather.c
- *       Support routines for scanning a plan via multiple workers.
+ *       Support routines for getting the result from a plan via multiple
+ *       workers.
*

Well I think "scanning a plan" is clear enough even if it's
technically a Scan. But I agree the second change is needed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#3Robert Haas
robertmhaas@gmail.com
In reply to: Robert Haas (#2)
Re: Minor comment edits in nodeGather.c

On Tue, Nov 24, 2015 at 9:31 PM, Robert Haas <robertmhaas@gmail.com> wrote:

On Tue, Nov 24, 2015 at 1:06 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:

While going through nodeGather.c, I noticed portions of the file header
comment that may have been obsoleted by recent revisions of the relevant
parellelism code. For example, there is a reference to PartialSeqScan node
which did not make it into the tree. Attached fixes it. Also, wondering if
the semantics of Gather node is that of Scan or more generic Plan? That is
to ask whether the following edit makes sense:

* nodeGather.c
- *       Support routines for scanning a plan via multiple workers.
+ *       Support routines for getting the result from a plan via multiple
+ *       workers.
*

Well I think "scanning a plan" is clear enough even if it's
technically a Scan. But I agree the second change is needed.

Err, even if it's NOT technically a scan.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#4Amit Langote
Langote_Amit_f8@lab.ntt.co.jp
In reply to: Robert Haas (#2)
Re: Minor comment edits in nodeGather.c

On 2015/11/25 11:31, Robert Haas wrote:

On Tue, Nov 24, 2015 at 1:06 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:

While going through nodeGather.c, I noticed portions of the file header
comment that may have been obsoleted by recent revisions of the relevant
parellelism code. For example, there is a reference to PartialSeqScan node
which did not make it into the tree. Attached fixes it. Also, wondering if
the semantics of Gather node is that of Scan or more generic Plan? That is
to ask whether the following edit makes sense:

* nodeGather.c
- *       Support routines for scanning a plan via multiple workers.
+ *       Support routines for getting the result from a plan via multiple
+ *       workers.
*

Well I think "scanning a plan" is clear enough even if it's
technically a Scan.

Okay, ripped that out in the attached.

Thanks,
Amit

Attachments:

nodegather-comment-fix.patchtext/x-diff; name=nodegather-comment-fix.patchDownload+2-1
#5Robert Haas
robertmhaas@gmail.com
In reply to: Amit Langote (#4)
Re: Minor comment edits in nodeGather.c

On Tue, Nov 24, 2015 at 9:43 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:

On 2015/11/25 11:31, Robert Haas wrote:

On Tue, Nov 24, 2015 at 1:06 AM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:

While going through nodeGather.c, I noticed portions of the file header
comment that may have been obsoleted by recent revisions of the relevant
parellelism code. For example, there is a reference to PartialSeqScan node
which did not make it into the tree. Attached fixes it. Also, wondering if
the semantics of Gather node is that of Scan or more generic Plan? That is
to ask whether the following edit makes sense:

* nodeGather.c
- *       Support routines for scanning a plan via multiple workers.
+ *       Support routines for getting the result from a plan via multiple
+ *       workers.
*

Well I think "scanning a plan" is clear enough even if it's
technically a Scan.

Okay, ripped that out in the attached.

Committed, thanks.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#6Amit Langote
Langote_Amit_f8@lab.ntt.co.jp
In reply to: Robert Haas (#5)
Re: Minor comment edits in nodeGather.c

On 2015/12/01 3:06, Robert Haas wrote:

On Tue, Nov 24, 2015 at 9:43 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:

On 2015/11/25 11:31, Robert Haas wrote:

Well I think "scanning a plan" is clear enough even if it's
technically a Scan.

Okay, ripped that out in the attached.

Committed, thanks.

Thanks!

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers