Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX - Mailing list pgsql-general

From Vivek Khera
Subject Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX
Date
Msg-id 53C6E75D-1334-43BF-865E-8D5B472C055E@khera.org
Whole thread Raw
In response to Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX  (Wes <wespvp@msg.bt.com>)
Responses Re: REINDEX on large DB vs. DROP INDEX/CREATE INDEX
List pgsql-general
On Feb 4, 2008, at 10:00 AM, Wes wrote:

> Just a follow-up on this...  The REINDEX took about 2 1/2 days.  I
> didn't
> gain much disk space back - a full backup takes just as long as
> before, but
> the vacuum time dropped from 30 hours to 3 hours.

what you need to do is compare the relpages from the pg_class table
for that index before and after.

if you didn't get much disk space back, make sure you have no long
running transactions that may have kept some older files open.


pgsql-general by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: lazy validation on complex criterion
Next
From: "Dave Page"
Date:
Subject: Re: Universal libpq.a ?