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

Re: Concerns about this release

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Don Baccus" <dhogaza(at)pacifier(dot)com>, "Jason Earl" <jason(dot)earl(at)simplot(dot)com>
Cc: "mlw" <markw(at)mohawksoft(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Concerns about this release
Date: 2001-12-19 02:40:30
Message-ID: GNELIHDDFBOCMGBFGEFOEENMCAAA.chriskl@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-hackers
> I think the new VACUUM is a great thing, and frankly I don't care all
> that much about the VACUUM FULL command issue.  I tend to take the view
> that command semantics shouldn't be changed if one can avoid it.  It's a
> view built on the fact that about twenty years of my past life were
> spent as a language implementor and dealing with customer feedback when
> I've been foolish enough to make semantics changes of this sort.

I actually just add 'vacuumdb -a -z -q' sort of thing to my crontab.  Which
version of VACCUM will vacuumdb be using in 7.2?  Will there be an option to
vacuumdb to run VACUUM FULL if it defaults to just VACUUM?

Chris


In response to

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2001-12-19 02:45:55
Subject: Re: Explicit config patch 7.2B4
Previous:From: Christopher Kings-LynneDate: 2001-12-19 02:24:33
Subject: Re: Concerns about this release

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