X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 835369DC86C for ; Mon, 16 Jan 2006 21:08:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 84913-02 for ; Mon, 16 Jan 2006 21:09:01 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 28DF99DC847 for ; Mon, 16 Jan 2006 21:08:55 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0H18tBC022961; Mon, 16 Jan 2006 20:08:55 -0500 (EST) To: me@alternize.com cc: pgsql-performance@postgresql.org Subject: Re: new to postgres (and db management) and performance already a problem :-( In-reply-to: <070501c61aee$ed450560$6402a8c0@iwing> References: <43CC1938.7020807@gmail.com> <18875.1137451410@sss.pgh.pa.us> <070501c61aee$ed450560$6402a8c0@iwing> Comments: In-reply-to message dated "Mon, 16 Jan 2006 23:48:10 +0100" Date: Mon, 16 Jan 2006 20:08:55 -0500 Message-ID: <22960.1137460135@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.089 required=5 tests=[AWL=0.089] X-Spam-Score: 0.089 X-Spam-Level: X-Archive-Number: 200601/213 X-Sequence-Number: 16691 writes: > in our db system (for a website), i notice performance boosts after a vacuum > full. but then, a VACUUM FULL takes 50min+ during which the db is not really > accessible to web-users. is there another way to perform maintenance tasks > AND leaving the db fully operable and accessible? You're not doing regular vacuums often enough. regards, tom lane