You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The developers in my team noticed that the comments that they left on the indexes were deleted.
Apparently, it is not a reindex concurrently operation that is being produced, but the creation of a new index and the removal of the old one.
I give a diff that may close this problem:
801,802c801
< pg_catalog.pg_relation_size(indexoid) as idxsize,
< coalesce(obj_description(cst.oid),obj_description(indexoid)) as comm
---
> pg_catalog.pg_relation_size(indexoid) as idxsize
819c818
< LEFT JOIN pg_catalog.pg_constraint cst ON
---
> LEFT JOIN pg_catalog.pg_constraint ON
902,903c901
< DROP INDEX CONCURRENTLY " . _dbh->quote_identifier($schema_name) . "." . _dbh->quote_identifier($tmp_index_name) . ";
< COMMENT ON INDEX " . _dbh->quote_identifier($schema_name) . "." . _dbh->quote_identifier($index_data->{indexname}) . " IS " . _dbh->quote($index_data->{comm}) ;
---
> DROP INDEX CONCURRENTLY " . _dbh->quote_identifier($schema_name) . "." . _dbh->quote_identifier($tmp_index_name) . ";";
The text was updated successfully, but these errors were encountered:
Yeah, I remembered this when I helped implement native reindex concurrently in postgresql 12.
Not sure if it makes sense now. The tool uses native reindex concurrently if available. Old-style create-rename-drop is a bit deprecated.
Uh oh!
There was an error while loading. Please reload this page.
The developers in my team noticed that the comments that they left on the indexes were deleted.
Apparently, it is not a reindex concurrently operation that is being produced, but the creation of a new index and the removal of the old one.
I give a diff that may close this problem:
The text was updated successfully, but these errors were encountered: