• R/O
  • HTTP
  • SSH
  • HTTPS

pg_hint_plan: List of commits

firtst release


RSS
Rev. Time Author
d518f03 REL12_1_3_5 2020-02-20 23:24:34 Kyotaro Horiguchi

Preparation for branch PG12

Change version to 12-1.3.5. Adjust SPEC file.

10efd8a REL11_1_3_5 2020-02-20 21:56:30 Kyotaro Horiguchi

Change version to 1.3.5.

cbe257d 2020-02-20 20:53:24 Kyotaro Horiguchi

Support PG12.

As the prepparation for making PG12 branch, change PG version to 12
and adjust for the latest PG12.

231a444 2020-02-20 20:19:44 Kyotaro Horiguchi

Change copyright year to 2020.

8fe6bea REL10_1_3_5 2020-02-20 20:12:38 Kyotaro Horiguchi

Change version to 1.3.5.

Version 1.3.4 for pg_hint_plan10 is skipped to make version number in
sync with pg_hint_plan11.

75ac46e 2020-02-20 19:58:27 Kyotaro Horiguchi

Change copyright year to 2020.

f170606 2020-02-20 19:06:11 Kyotaro Horiguchi

Change copyright year to 2020.

b09afed 2020-02-20 18:58:34 Kyotaro Horiguchi

Catch up core's change.

The commits 19ff710aaa, 19ff710aaa and d4b754c876 affected
core.c. Catch up them.

d6dcece REL96_1_2_6 2020-02-20 16:49:45 Kyotaro Horiguchi

Change version to 1.2.6.

7276432 2020-02-20 16:46:05 Kyotaro Horiguchi

Change copyright year to 2020.

c5a1d7d 2020-02-20 16:45:18 Kyotaro Horiguchi

Catch up core's change.

The commits 45f8eaa8e3 and 0255329a78 affected core.c. Catch up them.

9db100f PG94 2020-02-17 21:08:52 Kyotaro Horiguchi

Restore current hint state when returned from non-hinted query planning.

If no hint is given for the current level query, pg_hint_plan_planner
calls the next level of planner after erasing the
current_hint_state. But it forgot to restore the state before the
planning of the rest part of the current-level query. It is
(a-kind-of) broken by the commit 2c73975 and d1a839a but overlooked by
assuming the required side-effect of the fix. Get back the behavior
by restoring current_hint_state after returned from the lower level
planner with unhinted query.

Issue: https://github.com/ossc-db/pg_hint_plan/issues/30
Reported-by: higuchi-daisuke

4e63a22 PG95 2020-02-17 21:08:43 Kyotaro Horiguchi

Restore current hint state when returned from non-hinted query planning.

If no hint is given for the current level query, pg_hint_plan_planner
calls the next level of planner after erasing the
current_hint_state. But it forgot to restore the state before the
planning of the rest part of the current-level query. It is broken by
the commit 958c60d but overlooked among vast amount of behavioral
changes.. Get back the behavior by restoring current_hint_state after
returned from the lower level planner with unhinted query.

Issue: https://github.com/ossc-db/pg_hint_plan/issues/30
Reported-by: higuchi-daisuke

285b67d 2020-02-17 21:08:26 Kyotaro Horiguchi

Restore current hint state when returned from non-hinted query planning.

If no hint is given for the current level query, pg_hint_plan_planner
calls the next level of planner after erasing the
current_hint_state. But it forgot to restore the state before the
planning of the rest part of the current-level query. It is
(a-kind-of) broken by the commit d422966 but overlooked as an
inevitable side-effect of the fix. Get back the behavior by restoring
current_hint_state after returned from the lower level planner with
unhinted query.

Issue: https://github.com/ossc-db/pg_hint_plan/issues/30
Reported-by: higuchi-daisuke

1d86d3b 2020-02-17 21:08:15 Kyotaro Horiguchi

Restore current hint state when returned from non-hinted query planning.

If no hint is given for the current level query, pg_hint_plan_planner
calls the next level of planner after erasing the
current_hint_state. But it forgot to restore the state before the
planning of the rest part of the current-level query. It is
(a-kind-of) broken by the commit d422966 but overlooked as an
inevitable side-effect of the fix. Get back the behavior by restoring
current_hint_state after returned from the lower level planner with
unhinted query.

Issue: https://github.com/ossc-db/pg_hint_plan/issues/30
Reported-by: higuchi-daisuke

a9bcfa7 2020-02-17 21:08:03 Kyotaro Horiguchi

Restore current hint state when returned from non-hinted query planning.

If no hint is given for the current level query, pg_hint_plan_planner
calls the next level of planner after erasing the
current_hint_state. But it forgot to restore the state before the
planning of the rest part of the current-level query. It is
(a-kind-of) broken by the commit d422966 but overlooked as an
inevitable side-effect of the fix. Get back the behavior by restoring
current_hint_state after returned from the lower level planner with
unhinted query.

Issue: https://github.com/ossc-db/pg_hint_plan/issues/30
Reported-by: higuchi-daisuke

9d0d4e2 2020-02-17 21:07:20 Kyotaro Horiguchi

Restore current hint state when returned from non-hinted query planning.

If no hint is given for the current level query, pg_hint_plan_planner
calls the next level of planner after erasing the
current_hint_state. But it forgot to restore the state before the
planning of the rest part of the current-level query. It is
(a-kind-of) broken by the commit d422966 but overlooked as an
inevitable side-effect of the fix. Get back the behavior by restoring
current_hint_state after returned from the lower level planner with
unhinted query.

Issue: https://github.com/ossc-db/pg_hint_plan/issues/30
Reported-by: higuchi-daisuke

f204d75 2020-02-17 17:49:55 Kyotaro Horiguchi

Follow the core chnges.

Update core.c following the changes in the core. It makes difference
in the regression test result so update it, too.

789d4d7 2020-02-17 16:57:05 Kyotaro Horiguchi

Use proper type for non-integer GUC options.

pg_hint_plan internally preserved numeric options into integer
variable regardless of their types, which leads to unintentional
change of the values. Handle double values in the proper way.

ef5e864 2020-02-17 16:56:35 Kyotaro Horiguchi

Use proper type for non-integer GUC options.

pg_hint_plan internally preserved numeric options into integer
variable regardless of their types, which leads to unintentional
change of the values. Handle double values in the proper way.

0087813 2020-02-17 16:56:14 Kyotaro Horiguchi

Use proper type for non-integer GUC options.

pg_hint_plan internally preserved numeric options into integer
variable regardless of their types, which leads to unintentional
change of the values. Handle double values in the proper way.

7dcc96f 2020-02-17 16:55:02 Kyotaro Horiguchi

Use proper type for non-integer GUC options.

pg_hint_plan internally preserved numeric options into integer
variable regardless of their types, which leads to unintentional
change of the values. Handle double values in the proper way.

dd5ea96 2020-02-17 15:05:09 Kyotaro Horiguchi

Fix Rows hint parsing

This is a long standing bug that Rows hint with no parameter causees a
crash. Fixed the Rows hint parser.

f5ba122 2020-02-17 15:03:59 Kyotaro Horiguchi

Fix Rows hint parsing

This is a long standing bug that Rows hint with no parameter causees a
crash. Fixed the Rows hint parser.

ffc2832 2020-02-17 15:00:43 Kyotaro Horiguchi

Fix Rows hint parsing

This is a long standing bug that Rows hint with no parameter causees a
crash. Fixed the Rows hint parser.

4bd8229 2020-02-17 14:59:15 Kyotaro Horiguchi

Fix Rows hint parsing

This is a long standing bug that Rows hint with no parameter causees a
crash. Fixed the Rows hint parser.

52d9acd 2020-02-17 14:55:03 Kyotaro Horiguchi

Fix Rows hint parsing

This is a long standing bug that Rows hint with no parameter causees a
crash. Fixed the Rows hint parser.

516711b 2020-02-17 14:53:27 Kyotaro Horiguchi

Fix Rows hint parsing

This is a long standing bug that Rows hint with no parameter causees a
crash. Fixed the Rows hint parser.

788cf4b 2020-02-17 13:45:33 Kyotaro Horiguchi

Give correct query location to generate_normalized_query.

There was a thinko about query_loc of generate_normalized_query which
causes a crash. For example a query is following a sequence of
semicolons (by \; in psql input) longer than the length after the last
placeholder to the end of the query, the function causes assertion
failure. Anyway prepared statements lose that value so we just pass 0
as the query_loc for consistent behavior.

64249fb 2020-02-17 13:44:33 Kyotaro Horiguchi

Give correct query location to generate_normalized_query.

There was a thinko about query_loc of generate_normalized_query which
causes a crash. For example a query is following a sequence of
semicolons (by \; in psql input) longer than the length after the last
placeholder to the end of the query, the function causes assertion
failure. Anyway prepared statements lose that value so we just pass 0
as the query_loc for consistent behavior.

Show on old repository browser