From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Ildar Musin <i(dot)musin(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Index Onlys Scan for expressions |
Date: | 2016-09-03 11:37:40 |
Message-ID: | 8e492dfd-64c8-da64-7101-7a0ca9f7e352@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Ildar,
I've looked at this patch again today to do a bit more thorough review,
and I think it's fine. There are a few comments (particularly in the new
code in check_index_only) that need improving, and also a few small
tweaks in the walkers.
Attached is a modified v5 patch with the proposed changes - it's
probably easier than explaining what the changes should/might be.
I've added an XXX comment in check_index_only_expr_walker - ISTM we're
first explicitly matching Vars to index attributes, and then dealing
with expressions. But we loop over all index columns (including those
that can only really match Vars). Not sure if it makes any difference,
but is it worth differentiating between Var and non-Var expressions? Why
not to simply call match_index_to_operand() in both cases?
I've also tweaked a few comments to match project code style, and moved
a few variables into the block where they are used. But the latter is
probably matter of personal taste, I guess.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
indexonlyscan5-tomas.patch | binary/octet-stream | 8.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2016-09-03 12:25:32 | Re: autonomous transactions |
Previous Message | Simon Riggs | 2016-09-03 11:09:16 | Re: autonomous transactions |