电脑网站手机版怎么做现在济南可以正常出入吗

当前位置： 首页 > news >正文

电脑网站手机版怎么做,现在济南可以正常出入吗,网站备案 不备案,宠物美容师宠物美容培训学校1 总结 set_plan_references主要有两个功能#xff1a; 拉平#xff1a;生成拉平后的RTE列表#xff08;add_rtes_to_flat_rtable#xff09;。调整#xff1a;调整前每一层计划中varno的引用都是相对于本层RTE的偏移量。放在一个整体计划后#xff0c;需要指向一个统一…1 总结 set_plan_references主要有两个功能 拉平生成拉平后的RTE列表add_rtes_to_flat_rtable。调整调整前每一层计划中varno的引用都是相对于本层RTE的偏移量。放在一个整体计划后需要指向一个统一的RTE列表所以需要把varno调整下指向拉平后的RTE表。例如下面计划中RTE记录了6张表 1 → {rtekind RTE_RELATION, relid 16656, inh false, relkind 114 ‘r’} - student2 → {rtekind RTE_RELATION, relid 16671, inh false, relkind 114 ‘r’} - score3 → {rtekind RTE_JOIN, relid 0, inh false, relkind 0 } - {score join student}4 → {rtekind RTE_RELATION, relid 16661, inh false, relkind 114 ‘r’} - course5 → {rtekind RTE_JOIN, relid 0, inh false, relkind 0 } - {被优化掉的join course} Result节点的第一列是STUDENT.sname他的varno一开始是1varattno是2显然他不应该直接引用RTE中的某一张表因为Result节点的数据应该使用下面SORT节点中取出来的所以 varno被调整为-2表示引用OUTTER节点也就是LEFT树返回的结果varattno被调整1表示从结果中拿第一列。
explain SELECT STUDENT.sname, random(), SCORE.degree FROM STUDENT LEFT JOIN SCORE ON STUDENT.sno SCORE.sno LEFT JOIN COURSE ON SCORE.cno COURSE.cno ORDER BY STUDENT.sno;QUERY PLAN ————————————————————————————Result (cost182.67..213.27 rows2040 width54)- Sort (cost182.67..187.77 rows2040 width46)Sort Key: student.sno- Hash Right Join (cost34.75..70.53 rows2040 width46)Hash Cond: (score.sno student.sno)- Seq Scan on score (cost0.00..30.40 rows2040 width12)- Hash (cost21.00..21.00 rows1100 width42)- Seq Scan on student (cost0.00..21.00 rows1100 width42)上面用例经过set_plan_references调整前后的完整例子
2 数据结构 PlannerInfo 当前查询优化的状态包含了当前查询的所有信息 当前查询的目标列表target list子句例如WHERE、GROUP BY、ORDER BY 等范围表range table可用的索引信息统计信息子查询和参数信息优化器的各种临时数据和结果 PlannerGlobal 全局结构包含了跨多个查询级别的信息。例如一个包含子查询或CTE的查询中每个子查询都会有自己的 PlannerInfo结构会共享同一个PlannerGlobal。包含了 全局范围表finalrtable全局子计划列表全局初始化计划列表全局参数表达式列表重写规则和其他全局状态信息 varno宏 #define INNER_VAR (-1) /* reference to inner subplan / #define OUTER_VAR (-2) / reference to outer subplan / #define INDEX_VAR (-3) / reference to index column / #define ROWID_VAR (-4) / row identity column during planning */3 set_plan_references 1 计算全局flat_rtable set_plan_references → add_rtes_to_flat_rtable 首先把引用的rtable全部拉平到一个级别重新排列RTE。 具体在PlannerGlobal中构造全局范围表finalrtable所有子PlannerInfo共享的一套RTE。 p *root-glob-finalrtable $7 {type T_List, length 5, max_length 5, elements 0x3085520, initial_elements 0x3085520}add_rtes_to_flat_rtable后生成五个RTE RangeTblEntry {rtekind RTE_RELATION, relid 16656, inh false, relkind 114 r}RangeTblEntry {rtekind RTE_RELATION, relid 16671, inh false, relkind 114 r}RangeTblEntry {rtekind RTE_JOIN, relid 0, inh false, relkind 0}RangeTblEntry {rtekind RTE_RELATION, relid 16661, inh false, relkind 114 r}RangeTblEntry {rtekind RTE_JOIN, relid 0, inh false, relkind 0} PlannerInfo→PlannerGlobal 2 开始修正RTE的引用 set_plan_references → set_plan_refs 2.1 处理Result set_plan_refs → case T_Result: … 处理result子树→ plan-lefttree set_plan_refs(root, plan-lefttree, rtoffset); 递归处理左树→ plan-righttree set_plan_refs(root, plan-righttree, rtoffset); 递归处理右树 根据内层的sort节点重新排列result节点的三个var的varno和varattnoresult已经是最外层节点了当前使用到的var还是从sort节点继承的需要修复下。
处理前 vs 处理后
set_plan_refs处理T_Result节点 set_plan_refs……case T_Result:Result *splan (Result *) plan;if (splan-plan.lefttree ! NULL)set_upper_references(root, plan, rtoffset);……// subplan 是 SORT节点// subplan-targetlist 中返回三列STUDENT.sname, SCORE.degree, STUDENT.sno// 注意缺了一列random函数subplan_itlist build_tlist_index(subplan-targetlist); subplan-targetlist varno 1, varattno 2, vartype 1043varno 2, varattno 3, vartype 23varno 1, varattno 1, vartype 23 subplan_itlist subplan_itlist-tlist subplan-targetlistsubplan_itlist-vars[0] {varno 1, varattno 2, resno 1, varnullingrels 0x0}subplan_itlist-vars[1] {varno 2, varattno 3, resno 2, varnullingrels …}subplan_itlist-vars[2] {varno 1, varattno 1, resno 3, varnullingrels 0x0} foreach(l, plan-targetlist)…newexpr fix_upper_expr(…)…// 计算完成plan-targetlist output_targetlist;output_targetlist expr 0x308f0c8, resno 1, resname 0x2f4d670 sname varno OUTER_VAR -2, varattno 1, vartype 1043 expr 0x308f1b8, resno 2, resname 0x2f4d7e8 random funcid 1598, funcresulttype 701, funcretset false expr 0x308f258, resno 3, resname 0x2f4d928 degree varno OUTER_VAR -2, varattno 2, vartype 23 expr 0x308f2f8, resno 4, resname 0x0, ressortgroupref 1 varno OUTER_VAR -2, varattno 3, vartype 23
2.2 处理SORT set_plan_refs → case T_Sort: … 处理sort子树set_dummy_tlist_references→ plan-lefttree set_plan_refs(root, plan-lefttree, rtoffset); 递归处理左树→ plan-righttree set_plan_refs(root, plan-righttree, rtoffset); 递归处理右树
排序只需要引用下面一层的结果即可。 // These plan types dont actually bother to evaluate their // targetlists, because they just return their unmodified input // tuples. Even though the targetlist wont be used by the // executor, we fix it up for possible use by EXPLAIN (not to // mention ease of debugging — wrong varnos are very confusing).set_dummy_tlist_references2.3 处理Hash Right Join set_plan_refs → case T_HashJoin: … 处理join子树set_join_references→ plan-lefttree set_plan_refs(root, plan-lefttree, rtoffset); 递归处理左树→ plan-righttree set_plan_refs(root, plan-righttree, rtoffset); 递归处理右树 4 用例 explain SELECT STUDENT.sname, random(), SCORE.degree FROM STUDENT LEFT JOIN SCORE ON STUDENT.sno SCORE.sno LEFT JOIN COURSE ON SCORE.cno COURSE.cno ORDER BY STUDENT.sno;QUERY PLAN ————————————————————————————Result (cost182.67..213.27 rows2040 width54)- Sort (cost182.67..187.77 rows2040 width46)Sort Key: student.sno- Hash Right Join (cost34.75..70.53 rows2040 width46)Hash Cond: (score.sno student.sno)- Seq Scan on score (cost0.00..30.40 rows2040 width12)- Hash (cost21.00..21.00 rows1100 width42)- Seq Scan on student (cost0.00..21.00 rows1100 width42)