Re: Autovacuum in the backend

From: Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, Alvaro Herrera <alvherre(at)surnet(dot)cl>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Autovacuum in the backend
Date: 2005-06-17 07:16:16
Message-ID: 42B278C0.7050703@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

>> * Reduces the total amount of time the system spends vacuuming since
>> it only vacuums when needed.
>
>
> Can be easily done with cron.
>
>> * Keeps stats up-to-date automatically
>
>
> Which can be done with cron
>
>> * Eliminates newbie confusion
>
>
> RTFM
>
>> * Eliminates one of the criticisms that the public has against
>> PostgreSQL (justifed or not)
>
>
> Agreed.

I few weeks ago I have set up a database with more than 1.800 tables
(some complex business thing). inventing a clever cron-vacuum strategy
is almost impossible (or at least very painful). there should be a
mechanism (fortunately there is pg_autovacuum) to make this a bit more
practical.

in case of small databases this is not an issue.
small is always simple. complex and large are the major challenges.

best regards,

hans

--
Cybertec Geschwinde u Schoenig
Schoengrabern 134, A-2020 Hollabrunn, Austria
Tel: +43/664/393 39 74
www.cybertec.at, www.postgresql.at

In response to

Browse pgsql-general by date

  From Date Subject
Next Message stig erikson 2005-06-17 07:19:30 psql: FATAL: database "template1" is not currently accepting connections
Previous Message Joshua D. Drake 2005-06-17 07:03:26 Re: Autovacuum in the backend

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2005-06-17 07:34:46 Re: [PATCHES] Escape handling in strings
Previous Message Joshua D. Drake 2005-06-17 07:03:26 Re: Autovacuum in the backend