Skip site navigation (1) Skip section navigation (2)

Re: Partially corrupted table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Filip Hrbek <filip(dot)hrbek(at)plz(dot)comstar(dot)cz>, pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: Partially corrupted table
Date: 2006-08-30 02:10:10
Message-ID: 20517.1156903810@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> The underlined word is a field length word that evidently should contain
>> 8, but contains hex 8008.  This causes the tuple-data decoder to step
>> way past the end of the tuple and off into never-never land.

> Hmm, perhaps we could protect against "impossible" length words?

Perhaps.  I'm hesitant to add additional tests into the inner loop of
heap_deform_tuple and friends though.   It's not like it's going to do
anything to recover your data post-corruption :-(

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Kris JurkaDate: 2006-08-30 05:46:21
Subject: Re: BUG #2593: Improper implimentation of SQLException
Previous:From: Alvaro HerreraDate: 2006-08-30 00:18:36
Subject: Re: Partially corrupted table

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group