From: | Denis Braekhus <denis(at)startsiden(dot)no> |
---|---|
To: | Lonni Friedman <netllama(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: vacuumdb is failing with NUMBER OF INDEX TUPLES NOT |
Date: | 2004-05-06 21:00:25 |
Message-ID: | 409AA769.9070304@startsiden.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-nr2 (Windows XP)
iD8DBQFAmqdovsCA6eRGOOARAptYAJ0YF6+tGtyA55hqOf8UaF+q2JnN4wCfdQtV
r4nBoDljvFDGlXh3OhNSPcM=
=6xLx
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Harr | 2004-05-06 21:13:32 | Re: 7.2 or 7.4 for critical data? |
Previous Message | CSN | 2004-05-06 20:59:16 | regexp replace? |