diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-12-07 14:27:54 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-12-07 14:27:54 +0900 |
| commit | d43bd090a8fee81fe88eb1e9e15e30d30ee130ed (patch) | |
| tree | 1dc804aaa03c8313484cbe5b72a6fa1a0ba97b2e /src/backend/executor | |
| parent | 0bf62460bb9e86101d24e31e915c2e8922675296 (diff) | |
| download | postgresql-d43bd090a8fee81fe88eb1e9e15e30d30ee130ed.tar.gz postgresql-d43bd090a8fee81fe88eb1e9e15e30d30ee130ed.zip | |
Improve some error messages with invalid indexes for REINDEX CONCURRENTLY
An invalid index is skipped when doing REINDEX CONCURRENTLY at table
level, with INDEX_CORRUPTED used as errcode. This is confusing,
because an invalid index could exist after an interruption. The errcode
is switched to OBJECT_NOT_IN_PREREQUISITE_STATE instead, as per a
suggestion from Andres Freund.
While on it, the error messages are reworded, and a hint is added,
telling how to rebuild an invalid index in this case. This has been
suggested by Noah Misch.
Discussion: https://postgr.es/m/20231118230958.4fm3fhk4ypshxopa@awork3.anarazel.de
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions