Re: When do vacuumed pages/tuples become available for reuse?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Michael Lewis <mlewis(at)entrata(dot)com>
Cc: rihad <rihad(at)mail(dot)ru>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: When do vacuumed pages/tuples become available for reuse?
Date: 2019-04-12 05:14:54
Message-ID: 20190412051454.GN2144@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Apr 11, 2019 at 10:39:12PM -0600, Michael Lewis wrote:
> You can create (concurrently) an identical index with a new name, then drop
> old version concurrently and repeat for each. It doesn't help you figure
> out the root cause and how to prevent it from happening again, but gets you
> to a fresh start at least.

Please note that Postgres 12 has added support for REINDEX
concurrently. A huge advantage of that is the possibility to work on
indexes with constraints.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message rihad 2019-04-12 10:40:17 Re: When do vacuumed pages/tuples become available for reuse?
Previous Message Michael Lewis 2019-04-12 04:39:12 Re: When do vacuumed pages/tuples become available for reuse?