| From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
|---|---|
| To: | Siraj G <tosiraj(dot)g(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Index rebuilding strategy |
| Date: | 2025-09-24 20:50:56 |
| Message-ID: | 8E8DB597-41BA-4E6F-A792-13B8AA9238D2@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 24 Sep 2025, at 22:42, Siraj G <tosiraj(dot)g(at)gmail(dot)com> wrote:
>
> Hello Experts!
>
> What are the top pointers we should consider for index rebuild? Check its size, bloat estimate, heavy Updates/Deletes?
>
> Please highlight the best practices.
I think just any pointers of corruption, really. OS updates with differing collation implementations, known flaky hardware or driver issues, checksum discrepancies if you have those turned on and get any of those.
The need to rebuild indices should be quite rare. Regular vacuuming and analysing should take care of most of the need, with much of those happening automatically anyway (could need some tuning though).
Regards,
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-09-24 21:52:55 | Re: Index rebuilding strategy |
| Previous Message | Siraj G | 2025-09-24 20:42:05 | Index rebuilding strategy |