Re: Zeroing damaged pages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Zeroing damaged pages
Date: 2006-02-28 19:45:05
Message-ID: 23542.1141155905@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-02-28 19:48:31 Re: [HACKERS] Config file for psql
Previous Message Greg Stark 2006-02-28 19:25:12 Re: Dead Space Map

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2006-02-28 19:49:02 Re: [PATCH] Prompt for password on Windows platforms
Previous Message Neil Conway 2006-02-28 19:29:50 Re: <> operator