Re: vacuum vs vacuum full - Mailing list pgsql-general

From Ravi Krishna
Subject Re: vacuum vs vacuum full
Date
Msg-id 3C986184-C865-4069-B9D7-CA0580222080@yahoo.com
Whole thread Raw
In response to Re: vacuum vs vacuum full  (Paul Förster <paul.foerster@gmail.com>)
Responses Re: vacuum vs vacuum full
List pgsql-general

Experience shows that global index in Oracle lead to problems when dropping a partition. rebuilding an index, or other such nice administrative stuff, often leading to unnecessarily long downtimes.



I think Oracle fixed it later by allowing asynchronous update of global index after the detachment of partition.

ALTER TABLE TABLE_NAME DROP PARTITION PARTITION_NAME UPDATE INDEXES;

will immediately start maintenance of global index by cleaning it up asynchronously, while the index is marked valid and can be used by the applications.

DB2 also has the same feature for a long time and it works fine.

I am sure there are genuine use cases of global indexes.

pgsql-general by date:

Previous
From: Paul Förster
Date:
Subject: Re: vacuum vs vacuum full
Next
From: "David G. Johnston"
Date:
Subject: Re: How to select values in a JSON type of column?