Re: Missed compiler optimization issue in function select_rtable_names_for_explain - Mailing list pgsql-general

From Tom Lane
Subject Re: Missed compiler optimization issue in function select_rtable_names_for_explain
Date
Msg-id 6806.1716408332@sss.pgh.pa.us
Whole thread Raw
In response to Re: Missed compiler optimization issue in function select_rtable_names_for_explain  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Hash join and picking which result set to build the hash table with.
List pgsql-general
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> I think if we want to improve how this code is seen by the compiler by
> modifying it, we should just remove the NULL/NIL assignments.  It's a
> pretty arbitrary (and rather small) subset of fields being initialized,
> fields which very obviously have been zeroed by memset already, so I
> don't see any value in the explicit assignments.

I have to concede that it's unclear why we're filling just these
fields explicitly and not any others.  We're at least consistent:
all the callers of select_rtable_names do it the same way.

            regards, tom lane



pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: search_path and SET ROLE
Next
From: "Dirschel, Steve"
Date:
Subject: Hash join and picking which result set to build the hash table with.