| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Ravi Krishna <srkrishna(at)yahoo(dot)com> |
| Cc: | Cybertec Schönig & Schönig GmbH <laurenz(dot)albe(at)cybertec(dot)at>, Thomas Kellerer <shammat(at)gmx(dot)net>, PG List <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: vacuum vs vacuum full |
| Date: | 2020-11-18 14:59:30 |
| Message-ID: | 8AFEB6EE-02C5-4E7C-952C-34E639DAD2B2@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Ravi,
> On 18. Nov, 2020, at 15:30, Ravi Krishna <srkrishna(at)yahoo(dot)com> wrote:
>
> ALTER TABLE TABLE_NAME DROP PARTITION PARTITION_NAME UPDATE INDEXES;
IIRC the statement is
alter table <table> drop partition <partition> update *GLOBAL* indexes;
But we experienced big problems in the past which is why we changed all to local indexes. The situation may have improved in the last few years but we will not change back again. :-) Why should we?
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-11-18 15:11:37 | Re: vacuum vs vacuum full |
| Previous Message | Thomas Kellerer | 2020-11-18 14:55:31 | Re: How to select values in a JSON type of column? |