Re: auto vacuuming

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Gourish Singbal <gourish(at)gmail(dot)com>, elein <elein(at)varlena(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: auto vacuuming
Date: 2006-04-03 03:39:40
Message-ID: 27699.1144035580@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> The handwriting on the wall says that autovac will soon be on by
>> default, and perhaps become not-disablable some day after that
>> (like the second or third time we hear from someone who's lost
>> their data to XID wraparound after disabling it).

> I don't think we will see much people losing data to Xid wraparound
> anymore, now that the server refuses to work when the wraparound is
> imminent.

Well, how about the second or third time we get sued by someone whose
"must be up 24x7" database shuts down for lack of proper vacuuming?
I do think autovac is the wave of the future. The only reason it's
disablable now is that we don't think we've got all the bugs out.

If you read the old Berkeley Postgres papers, you'll see that a
"vacuum daemon" was always part of the system's basic design. (Hey
Elein, or anyone else who was there then --- was there ever a working
vacuum daemon, or was it just on paper?)

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message adey 2006-04-03 03:54:45 Re: Bloated pg_shdepend_depender_index
Previous Message Alvaro Herrera 2006-04-03 03:05:36 Re: auto vacuuming