pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: Shridhar Daithankar <shridhar_daithankar@myrealbox.com>
Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] More detail on settings for pgavd?
Date: Fri, 21 Nov 2003 13:49:58 -0800
Message-ID: <200311211349.58788.josh@agliodbs.com> (raw)
In-Reply-To: <3FBE891D.8010309@zeut.net>
References: <200311181558.45847.josh@agliodbs.com>
	<200311211323.19003.josh@agliodbs.com>
	<3FBE891D.8010309@zeut.net>

Matthew,

> Basically, I don't like the idea of modifying users databases, besides, 
> in the long run most of what needs to be tracked will be moved to the 
> system catalogs.  I kind of consider the pg_autvacuum database to 
> equivalent to the changes that will need to be made to the system catalogs.

OK.  As I said, I don't feel strongly about it.

> I certainly agree that less than 10% would be excessive, I still feel 
> that 10% may not be high enough though.   That's why I kinda liked the 
> sliding scale I mentioned earlier, because I agree that for very large 
> tables, something as low as 10% might be useful, but most tables in a 
> database would not be that large.

Yes, but I thought that we were taking care of that through the "threshold" 
value?

A sliding scale would also be OK.   However, that would definitely require a 
leap to storing per-table pg_avd statistics and settings.

> Only that pg_autovacuum isn't smart enough to kick off more than one 
> vacuum at a time.  Basically, pg_autovacuum issues a vacuum on a table 
> and waits for it to finish, then check the next table in it's list to 
> see if it needs to be vacuumed, if so, it does it and waits for that 
> vacuum to finish. 

OK, then, we just need to detect the condition of the vacuums "piling up" 
because they are happening too often.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco




view thread (35+ messages)  latest in thread

Message-ID: <200311211349.58788.josh@agliodbs.com>
Permalink:  ../200311211349.58788.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200311211349.58788.josh@agliodbs.com

 · 

reply

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-performance@postgresql.org
  Cc: josh@agliodbs.com, matthew@zeut.net, xzilla@users.sourceforge.net, shridhar_daithankar@myrealbox.com, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] More detail on settings for pgavd?
  In-Reply-To: <200311211349.58788.josh@agliodbs.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