| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "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 23:58:23 |
| Message-ID: | 05255888-38A1-4967-AD6F-2467B2ED65C6@pgedit.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Apr 2, 2006, at 11:39 PM, Tom Lane wrote:
>> 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.
Hopefully the could not sue if it is on by default but they turned it
off. But who knows :).
My reason for wanting to turn it off is that every time it would run
the fans on my development system would rev up. Very annoying in a
quiet environment where you are working on throw away tests that
don't need to eat CPU for vacuuming.
John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-04 00:03:57 | Re: auto vacuuming |
| Previous Message | Kevin Grittner | 2006-04-03 22:57:53 | Re: pg_stat_activity showing non-existent processes |