X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1B0C1D1B53A; Fri, 21 Nov 2003 22:00:43 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 93371-03; Fri, 21 Nov 2003 18:00:13 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 6E64CD1B515; Fri, 21 Nov 2003 18:00:10 -0400 (AST) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3956811; Fri, 21 Nov 2003 14:00:59 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "Matthew T. O'Connor" Subject: Re: [HACKERS] More detail on settings for pgavd? Date: Fri, 21 Nov 2003 13:49:58 -0800 User-Agent: KMail/1.4.3 Cc: Robert Treat , Shridhar Daithankar , pgsql-performance@postgresql.org, PostgreSQL-development References: <200311181558.45847.josh@agliodbs.com> <200311211323.19003.josh@agliodbs.com> <3FBE891D.8010309@zeut.net> In-Reply-To: <3FBE891D.8010309@zeut.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200311211349.58788.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/195 X-Sequence-Number: 4755 Matthew, > Basically, I don't like the idea of modifying users databases, besides,= =20 > in the long run most of what needs to be tracked will be moved to the=20 > system catalogs. I kind of consider the pg_autvacuum database to=20 > equivalent to the changes that will need to be made to the system catalog= s. OK. As I said, I don't feel strongly about it. > I certainly agree that less than 10% would be excessive, I still feel=20 > that 10% may not be high enough though. That's why I kinda liked the=20 > sliding scale I mentioned earlier, because I agree that for very large=20 > tables, something as low as 10% might be useful, but most tables in a=20 > database would not be that large. Yes, but I thought that we were taking care of that through the "threshold"= =20 value? A sliding scale would also be OK. However, that would definitely require = a=20 leap to storing per-table pg_avd statistics and settings. > Only that pg_autovacuum isn't smart enough to kick off more than one=20 > vacuum at a time. Basically, pg_autovacuum issues a vacuum on a table=20 > and waits for it to finish, then check the next table in it's list to=20 > see if it needs to be vacuumed, if so, it does it and waits for that=20 > vacuum to finish.=20 OK, then, we just need to detect the condition of the vacuums "piling up"= =20 because they are happening too often. --=20 -Josh Berkus Aglio Database Solutions San Francisco