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 86AD39DC944 for ; Tue, 17 Jan 2006 09:33:42 -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 19365-02 for ; Tue, 17 Jan 2006 09:33:45 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (serval.logix-tt.com [213.239.221.42]) by postgresql.org (Postfix) with ESMTP id D080C9DC807 for ; Tue, 17 Jan 2006 09:33:39 -0400 (AST) Received: from kingfisher.intern.logix-tt.com (Mc7a6.m.pppool.de [89.49.199.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id 9ABD324400F; Tue, 17 Jan 2006 14:40:02 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 8244718148C10; Tue, 17 Jan 2006 14:33:41 +0100 (CET) Message-ID: <43CCF235.1080009@logix-tt.com> Date: Tue, 17 Jan 2006 14:33:41 +0100 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Cc: me@alternize.com Subject: Re: new to postgres (and db management) and performance References: <43CC1938.7020807@gmail.com> <18875.1137451410@sss.pgh.pa.us> <070501c61aee$ed450560$6402a8c0@iwing> <22960.1137460135@sss.pgh.pa.us> In-Reply-To: <22960.1137460135@sss.pgh.pa.us> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.128 required=5 tests=[AWL=0.128] X-Spam-Score: 0.128 X-Spam-Level: X-Archive-Number: 200601/226 X-Sequence-Number: 16704 Hi, Tom, Tom Lane wrote: >>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. It may also help to increase the max_fsm_pages setting, so postmaster has more memory to remember freed pages between VACUUMs. HTH, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org