From: Jonah H. Harris <jonah.harris@gmail.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Campbell, Lance <lance@uiuc.edu>
Cc: posgres support <pgsql-admin@postgresql.org>
Subject: Re: Enhancement request
Date: Fri, 30 Nov 2007 17:53:01 -0500
Message-ID: <36e682920711301453x2d361iff5d3f8679606d3e@mail.gmail.com> (raw)
In-Reply-To: <20071130140005.18521c54@jd-laptop>
References: <B10E6810AC2A2F4EA7550D072CDE8760197E2C@SAB-FENWICK.sab.uiuc.edu>
<36e682920711301218m703b3c67s6f547fd7b9b60e7c@mail.gmail.com>
<7099.1196458205@sss.pgh.pa.us>
<36e682920711301332q1cce5db9qe44fb068fcd5608d@mail.gmail.com>
<7341.1196459304@sss.pgh.pa.us>
<20071130140005.18521c54@jd-laptop>
On Nov 30, 2007 5:00 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
> > So: show me a use case for this that will still make sense in a
> > mostly-autovacuum world.
>
> I think you are living in a different world than I am if you think it
> is a mostly-autovacuum world.
Same here.
> Yes autovacuum is great for general low use scenarios. Throw it at a
> database doing hundreds of thousands (or even millions) of transactions
> an hour that has relations that in the multiple hundred gig range and
> autovacuum is useless for a good portion of that database.
Yes, this is precisely the case I'm talking about. Every single
high-volume client we have or have consulted for is using custom
vacuuming. Autovacuum works fine for the common case, but it doesn't
handle high-volume databases very well yet.
> The thing is, it isn't nearly as special case for my environments. I
> have many customers, with many tables where autovacuum just doesn't cut
> it. We turn it on for say 80% of the relations but guess what... the
> important relations are still on some type of schedule through
> something like cron.
>
> I get your argument but surely adding SCHEMA isn't that much of a code
> bloat scenario. We don't even have to add another reserved word...
Agreed. It's very simple and won't add much code at all.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
Edison, NJ 08837 | http://www.enterprisedb.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jonah.harris@gmail.com, jd@commandprompt.com, tgl@sss.pgh.pa.us, lance@uiuc.edu
Subject: Re: Enhancement request
In-Reply-To: <36e682920711301453x2d361iff5d3f8679606d3e@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox