sr_plan looks like Oracle Outline system. It can be used to lock the execution plan. It is necessary if you do not trust the planner or able to form a better plan.

Dependencies: >= Python 3.2, Mako, pycparser

setsr_plan.write_mode= true;

Now plans for all subsequentrequests will be stored in the table sr_plans.It must be rememberedthat allrequests will bemaintained including duplicates.

Now plans for all subsequentqueries will be stored in the table sr_plans.Don't forgetthat allqueries will bestored including duplicates.

Making an example query:

select query_hashfrom sr_planswhere query_hash=10;

Now verify that your query is saved:

select query_hash, enable, valid, query, explain_jsonb_plan(plan)from sr_plans;

query_hash | enable | valid | query | explain_jsonb_plan

1783086253 | f | t |select query_hashfrom sr_planswhere query_hash=10; | Bitmap Heap Scanon sr_plans+

| | | | Recheck Cond: (query_hash=10)+

| | | |-> Bitmap Index Scanon sr_plans_query_hash_idx+

| | | | Index Cond: (query_hash=10)+

| | | |

explain_jsonb_plan function allows you to display explain execute the plan of which lies in jsonb. By default, all the plans are off, you need enable it:

update sr_plansset enable=truewhere query_hash=812619660;

update sr_plansset enable=truewhere query_hash=1783086253;

(812619660 for example only)

(1783086253 for example only)

After that, the plan for the query will be taken from the sr_plans.

In addition sr plan allows you to save a parameterized query plan. In this case, we have some constants in the query are not essential.