Fail REPACK in presence of !indisready indexes
Like VACUUM FULL, non-concurrent REPACK would try to rebuild such
indexes, which can sometimes succeed. Concurrent REPACK would however
fail. The inconsistency is not good, so make them both throw an error
quickly to force the user to make a decision on those indexes (most
likely, drop them).
Author: Álvaro Herrera <alvherre@kurilemu.de>
Reported-by: Zsolt Parragi <zsolt.parragi@percona.com>
Suggested-by: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Discussion: https://postgr.es/m/CAN4CZFO5A3YE0Dd-bn7eKrB20pECO3=U0wKg1z2rO=DxgWJJHQ@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/0c5d6269614e107d1d2d669f82f63f7e232b30c9
Modified Files
--------------
contrib/test_decoding/expected/repack.out | 16 +++++++
contrib/test_decoding/sql/repack.sql | 8 ++++
src/backend/commands/repack.c | 71 +++++++++++++++++++++++++++++++
3 files changed, 95 insertions(+)
