public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alban Hertroys <[email protected]>
To: Siraj G <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Index rebuilding strategy
Date: Wed, 24 Sep 2025 22:50:56 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAC5iy60ZstfyqPK2tmWLD_QdPTd-0FMfZHHKtyZsOSGZDjJRgw@mail.gmail.com>
References: <CAC5iy60ZstfyqPK2tmWLD_QdPTd-0FMfZHHKtyZsOSGZDjJRgw@mail.gmail.com>


> On 24 Sep 2025, at 22:42, Siraj G <[email protected]> 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.

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Index rebuilding strategy
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox