Hi,
There will be some problem to the index as
REINDEX is a maintenance operation and generally done when index is corrupted, bloated etc.
REINDEX is a locking operation hence it is risky to perform on a busy table,
I suggest in case of index corruption instead of reindexing you can :
create an index concurrently and remove the old index in off peak hours.
Thanks & Regards,
Ajinkya Bangale
Database Administrator
ajinkya.bangale@xxxxxxxxxxxxxx
Office: +919552687400/8400
Ajinkya Bangale
Database Administrator
ajinkya.bangale@xxxxxxxxxxxxxx
Office: +919552687400/8400
On Tue, Feb 17, 2015 at 8:43 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
"Jan-Peter Seifert" <Jan-Peter.Seifert@xxxxxx> writes:
> I wonder whether canceling a REINDEX of a database is safe ( PostgreSQL v9.2.7 ).
Sure. If it weren't cancel-safe, it wouldn't be crash-safe either.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
