From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | James Hunter <james(dot)hunter(dot)pg(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [PATCH] Move clause_sides_match_join() into pathnode.h |
Date: | 2024-10-15 08:20:48 |
Message-ID: | CAApHDvpSBsvTo7wnYYSbx9ixMJnCBSndrvAmLBL--fzST6=9_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 11 Oct 2024 at 04:25, James Hunter <james(dot)hunter(dot)pg(at)gmail(dot)com> wrote:
> Moved into restrictinfo.h, instead, in next revision.
Thanks. Pushed.
> > (I really wonder how much the inlining is giving us given that the
> > function itself calls other non-inlineable functions)
>
> I wondered the same! But, at least the branch can be inlined?
Do you mean function call? As far as I see it, that's the only
advantage. There are no branches that can be eliminated from
constant-folding.
I imagine the original version was only inlined to help coax the
compiler into inlining, which I imagine it would have done anyway if
there was just a single usage of the static function. Probably the
analyzejoins.c version just copied the original joinpath.c version. I
didn't check the history to know if that's actually true.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Jingtang Zhang | 2024-10-15 08:22:32 | Re: Use WALReadFromBuffers in more places |
Previous Message | Anthonin Bonnefoy | 2024-10-15 08:11:40 | Re: Set query_id for query contained in utility statement |