Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id B620E2E005B for ; Mon, 7 Apr 2008 13:27:16 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 14076-02-4 for ; Mon, 7 Apr 2008 13:27:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by developer.postgresql.org (Postfix) with ESMTP id 0755D2E008F for ; Mon, 7 Apr 2008 13:27:02 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id m38so1760244waf.5 for ; Mon, 07 Apr 2008 09:27:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=wWzB8MWWalErk9JMm/73J/m95YC8TuP51YU+5P/MYrc=; b=jwUYIg7sxoGsKqRwtZmrLWmfE5iljXsIumQ8I7BCzzu+ZdVjN+1LpgsSpa4P4Iw1rNMwTDKUYcRGbFp/yJ056mnfFFMRiWN712+ZtueBU6J6cHVDWqZTyalAajdkrupnm/ZB9fEbvUusvS7bj1DOUjNjIr5yElH0JyPksviEpNg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aPXfg/jNIEDMqO0YoKv6AseFI1ysAPxU/FMBoh9KrVhWZ9eiTPvUSE8MHp6go+xobJ81ippfOTKeIkvVrm9T+5IKT0MTf6yKj0AOqF3JMmq9E/vQoYgtWyUWCTJLu28Ctsn+aWg0FfX1mezfjfEiB8D4BxrAKW9OGpt9MdQgCUM= Received: by 10.114.191.1 with SMTP id o1mr6172730waf.117.1207585622053; Mon, 07 Apr 2008 09:27:02 -0700 (PDT) Received: by 10.114.137.7 with HTTP; Mon, 7 Apr 2008 09:27:02 -0700 (PDT) Message-ID: Date: Mon, 7 Apr 2008 10:27:02 -0600 From: "Scott Marlowe" To: "Carol Walter" Subject: Re: Tuning Cc: pgsql-admin@postgresql.org In-Reply-To: <6F737A76-FC25-4876-A6E0-163B87ECFAB0@indiana.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6F737A76-FC25-4876-A6E0-163B87ECFAB0@indiana.edu> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/54 X-Sequence-Number: 28818 On Mon, Apr 7, 2008 at 9:33 AM, Carol Walter wrote: > I have some questions about tuning. The PostgreSQL documentation says that > you don't need to worry about index maintenance and tuning with PostgreSQL. > I'm used to systems that work a lot better if they are periodically re-orged > or re-indexed. Is it true that one need not be concerned with this? I'm > certain that the databases must require some human intervention. What kind > of tuning or other intervention are you doing. What kind of tools are > available and are being used. Not sure where in the docs it exactly says to never worry about your indexes. While most access patterns can indeed be handled fine by autovacuum, you can use the reindex command in pgsql to optimize your indexes if they're chock full of empty space that can't be reclaimed by vacuum. You can monitor things like index and table bloat with the pg_stat_* series of views.