On 8/3/20 12:58 PM, Christophe Pettus wrote
On Aug 3, 2020, at 10:20, Konireddy Rajashekar <rajkonireddy@xxxxxxxxx> wrote:
Could you please suggest any ideal approach to tackle this ?
You can do CREATE INDEX CONCURRENTLY to build a new index with the same definition, and when that is complete, drop the old index. The locking that is required here is modest: CREATE INDEX CONCURRENTLY needs to lock the table briefly at a couple of points in the operation, and dropping the old index requires a brief lock on the table. It is, however, much less overall lock time than REINDEX would be.
Of course, you need enough disk space... :)
--
Angular momentum makes the world go 'round.
