Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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

In response to

pgsql-admin by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group