Boy ****I'LL**** say you lucked out! Postgres is good stuff ... it withstood that problem, I get
more impressed every day by it.
2/11/2003 1:50:40 PM, Jonathan Ellis <jonathan@carnageblender.com> wrote:
>Tom Lane wrote:
>> Jonathan Ellis <jonathan@carnageblender.com> writes:
>>> when trying to vacuum I got this:
>>> FATAL 2: PageIndexTupleDelete: corrupted page pointers: lower = 21845,
>>> upper = 21845, special = 21845
>>
>> Hmm ... 21845 = hex 5555, and you have the same in at least three places
>> in the page header ... you have a badly clobbered page there. Check
>> for hardware problems.
>
>memtest86 said 3 of my 4 dimms had bad spots. ouch.
>
>>> I experimentally determined the problem was with my "users" table. I
>>> did a pg_dump -t on it, manually deleted all triggers, dropped the
>>> table, and loaded from the dump. This fixed it.
>>
>> But you probably lost a few rows, like whatever was on the trashed page
>> (or pages?). Can you do anything to crosscheck the data you have left?
>
>All the referential integrity triggers restored w/o complaining. (And
>_every_ entry in this table is used as a key in at least two other
>tables.) Looks like I lucked out.
>
>-Jonathan
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org
>
