pgsql: Skip setting up shared instrumentation for Hash node if not need

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Skip setting up shared instrumentation for Hash node if not need
Date: 2018-02-05 03:15:06
Message-ID: E1eiXFK-0008CC-H7@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Skip setting up shared instrumentation for Hash node if not needed.

We don't need to set up the shared space for hash join instrumentation data
if instrumentation hasn't been requested. Let's follow the example of the
similar Sort node code and save a few cycles by skipping that when we can.

This reverts commit d59ff4ab3 and instead allows us to use the safer choice
of passing noError = false to shm_toc_lookup in ExecHashInitializeWorker,
since if we reach that call there should be a TOC entry to be found.

Thomas Munro

Discussion: https://postgr.es/m/E1ehkoZ-0005uW-43%40gemulon.postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/05d0f13f0701d84e4e6784da336aabcc2dfc8ade

Modified Files
--------------
src/backend/executor/nodeHash.c | 23 +++++++++++++++++------
1 file changed, 17 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-02-05 03:15:29 Re: pgsql: Fix another instance of unsafe coding for shm_toc_lookup failure
Previous Message Thomas Munro 2018-02-05 02:47:13 Re: pgsql: Fix another instance of unsafe coding for shm_toc_lookup failure