From: | "Tim Perdue" <perdue(at)raccoon(dot)com> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Weird Errors in 6.4.2 - Indexes/Vacuuming |
Date: | 1999-05-07 11:16:25 |
Message-ID: | 003101be987b$0c585ef0$0b8c5aa5@timnt.weather.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
It seems there are some pretty critical problems in the indexes and/or
vacuuming code in PostgreSQL 6.4.2. I've mentioned this before, but never
get any clues back.
Here are some error codes that I get almost every nite when I vacuum....
NOTICE: AbortTransaction and not in in-progress state
ERROR: heap_delete: (am)invalid tid
...And...
NOTICE: Rel pg_statistic: Uninitialized page 2 - fixing
ERROR: Tuple is too big: size 15248
Can anyone please shed some light on this? I don't have any code that would
be creating tuples bigger than 8100k, so the 15248 is not possible.
In addition, the "tuple is too big" error goes away in the second vacuum.
It's there one night, but not the next, and I never delete records out of
this database. The first errors up there require me to drop the indexes on
this 3GB table and rebuild. That's a pain.
Tim Perdue
PHPBuilder.com / GotoCity.com / Geocrawler.com
From | Date | Subject | |
---|---|---|---|
Next Message | D'Arcy J.M. Cain | 1999-05-07 11:48:32 | Re: [HACKERS] pg_dump problem? |
Previous Message | Michael Contzen | 1999-05-07 10:11:30 | Re: [HACKERS] Hashjoin status report |