aboutsummaryrefslogtreecommitdiff
path: root/contrib/jsonb_plperl/jsonb_plperl.control
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-07-29 09:58:49 +0900
committerMichael Paquier <michael@paquier.xyz>2019-07-29 10:01:09 +0900
commit28bbf7a81b3a30504cc7dfdbd76b410d1f127b8e (patch)
tree45a27d28e334525385b3de95f48f528146ca74f9 /contrib/jsonb_plperl/jsonb_plperl.control
parent180825fe43ece9bf13c27929b7fdeec5a457e9c3 (diff)
downloadpostgresql-28bbf7a81b3a30504cc7dfdbd76b410d1f127b8e.tar.gz
postgresql-28bbf7a81b3a30504cc7dfdbd76b410d1f127b8e.zip
Fix handling of expressions and predicates in REINDEX CONCURRENTLY
When copying the definition of an index rebuilt concurrently for the new entry, the index information was taken directly from the old index using the relation cache. In this case, predicates and expressions have some post-processing to prepare things for the planner, which loses some information including the collations added in any of them. This inconsistency can cause issues when attempting for example a table rewrite, and makes the new indexes rebuilt concurrently inconsistent with the old entries. In order to fix the problem, fetch expressions and predicates directly from the catalog of the old entry, and fill in IndexInfo for the new index with that. This makes the process more consistent with DefineIndex(), and the code is refactored with the addition of a routine to create an IndexInfo node. Reported-by: Manuel Rigger Author: Michael Paquier Discussion: https://postgr.es/m/CA+u7OA5Hp0ra235F3czPom_FyAd-3+XwSJmX95r1+sRPOJc9VQ@mail.gmail.com Backpatch-through: 12
Diffstat (limited to 'contrib/jsonb_plperl/jsonb_plperl.control')
0 files changed, 0 insertions, 0 deletions