Re: auto vacuuming

From: "Joshua D(dot) Drake" <jd(at)commandprompt(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>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: auto vacuuming
Date: 2006-04-01 03:32:46
Message-ID: 442DF45E.4090409@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

>
> 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).
>
> So if there's a really convincing use-case for locking autovac out
> of specific databases, we'd better hear it soon.

Sure.. a database that has over 2500 connections per a directly
connected Java rich client... I don't want autovac running on it from
8-8 but after that I will run my own vacuum process.

I am smart enough to manage my data. If I want autovac I will turn it on.

Joshua D. Drake

>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Rajesh Kumar Mallah 2006-04-01 04:23:41 Re: FW: Setting up of PITR system.
Previous Message Tom Lane 2006-04-01 03:29:01 Re: auto vacuuming