mirror of
https://ghfast.top/https://github.com/discourse/discourse-translator.git
synced 2026-07-16 11:46:33 +08:00
The previous version of the migration is not idempotent and can result in indexes created but marked as "invalid" by Postgres. Per postgres documentation: If a problem arises while scanning the table, such as a deadlock or a uniqueness violation in a unique index, the CREATE INDEX command will fail but leave behind an "invalid" index. This index will be ignored for querying purposes because it might be incomplete; however it will still consume update overhead. The recommended recovery method in such cases is to drop the index and try again to perform CREATE INDEX CONCURRENTLY. |
||
|---|---|---|
| .. | ||
| 20210429154318_remove_empty_translation_custom_fields.rb | ||
| 20230323110557_rename_translator_azure_custom_domain_site_setting.rb | ||
| 20250205082400_create_translation_tables.rb | ||
| 20250205082401_move_translations_custom_fields_to_table.rb | ||
| 20250210171147_hyphenate_translator_locales.rb | ||
| 20250224120505_cleanup_ai_translations.rb | ||
| 20250227074505_rename_translator_site_settings.rb | ||
| 20250313082243_create_translation_indexes.rb | ||