| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Automatically force zero_damaged_pages while InRecovery? |
| Date: | 2003-11-29 19:46:03 |
| Message-ID: | 20031129194603.GA16671@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 29, 2003 at 11:31:03AM -0800, Joe Conway wrote:
> Tom Lane wrote:
> >This failure is actually entirely pointless, because (AFAIK) any page
> >that is brought in during WAL recovery is going to be overwritten in
> >toto from the WAL log. So it would be safe to run WAL recovery with
> >zero_damaged_pages enabled. Rather than expecting DBAs to think of that
> >under the stress of a crashed-database situation, I propose that we do
> >it for them:
>
> Sounds like a good idea to me.
Yes, but is the error message going to stay verbatim? Maybe the
category could be decreased ...
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Everybody understands Mickey Mouse. Few understand Hermann Hesse.
Hardly anybody understands Einstein. And nobody understands Emperor Norton."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-29 19:55:13 | Re: Automatically force zero_damaged_pages while InRecovery? |
| Previous Message | Marc G. Fournier | 2003-11-29 19:41:28 | 7.3.5 to be released this week ... |