From: | Lonni Friedman <netllama(at)gmail(dot)com> |
---|---|
To: | Denis Braekhus <denis(at)startsiden(dot)no>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT THE SAME AS HEAP |
Date: | 2004-05-07 13:14:22 |
Message-ID: | 7c1574a90405070614536c9fe2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for your reply. I thought (perhaps erroneously) that there
wasn't any real difference between dropping an index then recreating
it, and just reindexing an index?
On Thu, 06 May 2004 23:00:25 +0200, Denis Braekhus <denis(at)startsiden(dot)no> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Lonni Friedman wrote:
> |>>Then nothing for a month after going to 7.3.4, and now its happening
> |>>every vacuumdb run again.
> |>Once the complaint starts appearing, I'd expect it to continue until you
> |>reindex the index.
> | That's exactly what happens. It consistantly errors until reindexed.
> | Any suggestions? thanks.
>
> A long shot, but we experienced a similar kind of issue, though our
> dataset was a bit different (not so many large objects).
> After having reindexed a couple of times with about the same results
> (working fine for some time, then complaining again), I dropped the
> index and recreated it. That seemed to fix the issue at our
> installation, we had no such problems after that. Ran for some months
> after that before I took the plunge and moved to 7.4..
>
> This might not at all work for you though, and as removing the index
> will probably kill your performance for a while I cannot promise you a
> fix with this workaround..
>
> Best Regards
> - --
> Denis
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Ridge | 2004-05-07 14:23:48 | Re: Changing the size of a varchar field |
Previous Message | Együd Csaba | 2004-05-07 12:11:25 | Re: Removing OIDs without recreate |