Nov 13, 2018
Changed version to 1.2.4
Previously parse_messages and message_level were binded to the same
internal variable. Separate the two GUCs. On the way doing this some
mssages that did not honor the variable were fixed. Default behavior
is not changed but the the two variables works differently from the
previous version, perhaps closer to expected.
Nov 13, 2018
Changed version to 1.1.7
Previously parse_messages and message_level were binded to the same
internal variable. Separate the two GUCs. On the way doing this some
mssages that did not honor the variable were fixed. Default behavior
is not changed but the the two variables works differently from the
previous version, perhaps closer to expected.
Nov 13, 2018
Changed version to 1.1.7
Previously parse_messages and message_level were binded to the same
internal variable. Separate the two GUCs. On the way doing this some
mssages that did not honor the variable were fixed. Default behavior
is not changed but the the two variables works differently from the
previous version, perhaps closer to expected.
Nov 13, 2018
Change target version to PG11 and fix the SPEC file
Change targetr version to PG11. SPEC file was changed so that genearte
a subpackage llvmjit, which installs a bitcode file needed for JIT
compilation.
Nov 13, 2018
Changed version to 1.3.2
Previously parse_messages and message_level were binded to the same
internal variable. Separate the two GUCs. On the way doing this some
mssages that did not honor the variable were fixed. Default behavior
is not changed but the the two variables works differently from the
previous version, perhaps closer to expected.
Jun 8, 2018
Change version to 1.2.3.
1.2.2 has a crash bug in Describe message of extended protocol
path. If server receives the message after invalidation of
corresponding query cache, pg_hint_plan crashes.

On the way fixing it, this version took in the following commit of
core.

64ad85860c Change more places to be less trusting of RestrictInfo.is_pushed_down.
Jun 8, 2018
Change version to 1.1.6.
1.1.5 has a crash bug in Describe message of extended protocol
path. If server receives the message after invalidation of
corresponding query cache, pg_hint_plan crashes.

On the way fixing it, this version took in the following commit of
core.

80e12a6218 Change more places to be less trusting of RestrictInfo.is_pushed_down.
Jun 8, 2018
Change version to 1.1.6.
1.1.5 has a crash bug in Describe message of extended protocol
path. If server receives the message after invalidation of
corresponding query cache, pg_hint_plan crashes.

On the way fixing it, this version took in the following commit of
core.

58fec95268 Change more places to be less trusting of RestrictInfo.is_pushed_down.
Jun 8, 2018
Change version to 1.1.6.
1.1.5 has a crash bug in Describe message of extended protocol
path. If server receives the message after invalidation of
corresponding query cache, pg_hint_plan crashes.

On the way fixing it, this version took in the following commit of
core.

9680c120e5 Change more places to be less trusting of RestrictInfo.is_pushed_down.
Jun 8, 2018
Change version to 1.3.1.
1.3.0 has a crash bug in Describe message of extended protocol
path. If server receives the message after invalidation of
corresponding query cache, pg_hint_plan crashes.

On the way fixing it, this version took in the following commits of
core and pg_stat_statements.

8b6294c7a5 Change more places to be less trusting of RestrictInfo.is_pushed_down.
83f2061dd0 Teach contrib/pg_stat_statements to handle multi-statement commands better.
0bb51aa967 Improve parsetree representation of special functions such as CURRENT_DATE.