Re: [HACKERS] Zeroing damaged pages

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Zeroing damaged pages
Date: 2006-03-06 05:14:00
Message-ID: 200603060514.k265E0N15393@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> On Thu, 2006-02-23 at 11:54 -0500, Tom Lane wrote:
> >>> Hmm .... it'd probably be a good idea to force zero_damaged_pages OFF in
> >>> the autovac subprocess. That parameter is only intended for interactive
> >>> use --- as you say, autovac would be a rather nasty loose cannon if it
> >>> fired up with this parameter ON.
>
> > I am wondering if we should prevent autovac from running if
> > zero_damaged_pages is set in postgresql.conf.
>
> What's wrong with just turning it off locally in the autovac process?
>
> If the admin prefers autovac not run at all while he's fooling around,
> he can disable it in postgresql.conf (or perhaps even better, run in
> single-user mode). But I don't think it's appropriate to force that
> decision on him.

Done.

--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com

+ If your life is a hard drive, Christ can be your backup. +

Attachment Content-Type Size
unknown_filename text/plain 730 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ben Chelf 2006-03-06 05:35:45 Coverity Open Source Defect Scan of PostgreSQL
Previous Message Bruce Momjian 2006-03-06 05:06:28 Re: Uninstall script errors

Browse pgsql-patches by date

  From Date Subject
Next Message Albe Laurenz 2006-03-06 08:00:47 Re: [HACKERS] LDAP auth
Previous Message Bruce Momjian 2006-03-06 04:47:24 Re: fix of some issues with multi-line query editing