From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Detecting corrupted pages earlier |
Date: | 2003-04-03 04:36:00 |
Message-ID: | 20030403043600.GE6760@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 02, 2003 at 11:10:13PM -0500, Tom Lane wrote:
> What I'd really prefer to see is not a ZERO_DAMAGED_PAGES setting,
> but an explicit command to "DESTROY PAGE n OF TABLE foo". That would
> make you manually admit defeat for each individual page before it'd
> drop data. But I don't presently have time to implement such a command
> (any volunteers out there?). Also, I could see where try-to-dump, fail,
> DESTROY, try again, lather, rinse, repeat, could get pretty tedious on a
> badly damaged table.
Huh, and what if I accidentaly mistype the number and destroy a valid
page? Maybe the command should only succeed if it confirms that the
page is corrupted.
There could also be "DESTROY ALL PAGES" and/or "DESTROY n PAGES"
commands, where the latter zeroes the first n corrupted pages in the
table, for the case with lots of corrupted pages. Maybe a command for
getting a list of the corrupted pages is useful?
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"La verdad no siempre es bonita, pero el hambre de ella si"
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-04-03 04:36:36 | Re: Detecting corrupted pages earlier |
Previous Message | Tom Lane | 2003-04-03 04:10:13 | Re: Detecting corrupted pages earlier |