PostgreSQL executes queries using cost-based optimizer, and sometimes fails to choose most optimized execution plan or some types of queries. In such cases, pg_hint_plan helps users to guide the planner to choose the plans they want by putting some nstructions - call them hints - in the comments prefixed to the SQL statement body. No need to rewrite statement tself nor change some GUC parameters elsewhere.
pg_hint_plan 1.3.2 for PG10 is released.
The behavior of GUC variables message_level and parse_messages is changed. These variables used to be the same variable internally but they became to work separately now. Several messages whose error level didn't follow the variables are fixed along with.
PG10向けの pg_hint_plan 1.3.2 をリリースします。
GUC変数 message_level と parse_messages の挙動が修正されました。以前はこれらの変数は内部的に同一のものでしたが、分離されました。同時に一部のメッセージのエラーレベルがこの変数に従っていなかった点についても修正されています。
Fork