pgsql: Code review for nodeGatherMerge.c.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Code review for nodeGatherMerge.c.
Date: 2017-08-30 21:21:18
Message-ID: E1dnAQI-0004tt-UA@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Code review for nodeGatherMerge.c.

Comment the fields of GatherMergeState, and organize them a bit more
sensibly. Comment GMReaderTupleBuffer more usefully too. Improve
assorted other comments that were obsolete or just not very good English.

Get rid of the use of a GMReaderTupleBuffer for the leader process;
that was confusing, since only the "done" field was used, and that
in a way redundant with need_to_scan_locally.

In gather_merge_init, avoid calling load_tuple_array for
already-known-exhausted workers. I'm not sure if there's a live bug there,
but the case is unlikely to be well tested due to timing considerations.

Remove some useless code, such as duplicating the tts_isempty test done by
TupIsNull.

Remove useless initialization of ps.qual, replacing that with an assertion
that we have no qual to check. (If we did, the code would fail to check
it.)

Avoid applying heap_copytuple to a null tuple. While that fails to crash,
it's confusing and it makes the code less legible not more so IMO.

Propagate a couple of these changes into nodeGather.c, as well.

Back-patch to v10, partly because of the possibility that the
gather_merge_init change is fixing a live bug, but mostly to keep
the branches in sync to ease future bug fixes.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/04e9678614ec64ad9043174ac99a25b1dc45233a

Modified Files
--------------
src/backend/executor/nodeGather.c | 21 ++--
src/backend/executor/nodeGatherMerge.c | 185 ++++++++++++++++++---------------
src/include/nodes/execnodes.h | 46 ++++----
3 files changed, 138 insertions(+), 114 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2017-08-30 22:16:59 Re: Re: [COMMITTERS] pgsql: pg_rewind: Fix some problems when copying files >2GB.
Previous Message Tom Lane 2017-08-30 17:18:30 pgsql: Separate reinitialization of shared parallel-scan state from Exe