From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: REINDEX checking of index constraints |
Date: | 2013-07-21 20:47:00 |
Message-ID: | 51EC48C4.1050702@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/21/2013 11:30 AM, Josh Berkus wrote:
> Noah,
>
>> Attached patch just restores the old behavior. Would it be worth preserving
>> the ability to fix an index consistency problem with a REINDEX independent
>> from related heap consistency problems such as duplicate keys?
>
> I would love to have two versions of REINDEX, one which validated and
> one which didn't. Maybe a ( validate off ) type check?
Cancel this. I just did some tests, and there amount of time required
for the validation (at least, in simple two-column table test) is < 10%
of the time required to reindex in general. At that difference, we
don't need two options.
Unless you're asking if we want a command to check the index validity
without rebuilding it? That might be more valuable ...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2013-07-21 22:11:25 | Re: Proposal: template-ify (binary) extensions |
Previous Message | Markus Wanner | 2013-07-21 20:30:59 | Re: Proposal: template-ify (binary) extensions |