X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A7C53D1CCE0; Thu, 20 Nov 2003 19:21:46 +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 95691-05; Thu, 20 Nov 2003 15:21:16 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 08848D1D163; Thu, 20 Nov 2003 15:20:59 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hAKJKO19006001; Thu, 20 Nov 2003 14:20:24 -0500 (EST) To: Chester Kustarz Cc: Josh Berkus , pgsql-performance@postgresql.org, PostgreSQL-development Subject: Re: [HACKERS] More detail on settings for pgavd? In-reply-to: References: Comments: In-reply-to Chester Kustarz message dated "Thu, 20 Nov 2003 13:48:21 -0500" Date: Thu, 20 Nov 2003 14:20:24 -0500 Message-ID: <6000.1069356024@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/178 X-Sequence-Number: 4738 Chester Kustarz writes: > i have some tables which are insert only. i do not want to vacuum them > because there are never any dead tuples in them and the vacuum grows the > indexes. Those claims cannot both be true. In any case, plain vacuum cannot grow the indexes --- only a VACUUM FULL that moves a significant number of rows could cause index growth. > vacuum is to reclaim dead tuples. this means it depends on update and > delete. analyze depends on data values/distribution. this means it depends on > insert, update, and delete. thus the dependencies are slightly different > between the 2 operations, an so you can come up with use-cases that > justify running either more frequently. Agreed. regards, tom lane