From: Michael Riess <mlriess@gmx.de>
To: pgsql-performance@postgresql.org
Subject: Re: Autovacuum / full vacuum
Date: Tue, 17 Jan 2006 15:50:38 +0100
Message-ID: <dqj07o$2tl4$1@news.hub.org> (raw)
In-Reply-To: <m3zmlvq7c9.fsf@mobile.int.cbbrowne.com>
References: <dqigaf$1b98$1@news.hub.org>
<43CCC711.504@familyhealth.com.au>
<dqih4p$1clg$1@news.hub.org>
<m3zmlvq7c9.fsf@mobile.int.cbbrowne.com>
Well,
I think that the documentation is not exactly easy to understand. I
always wondered why there are no examples for common postgresql
configurations. All I know is that the default configuration seems to be
too low for production use. And while running postgres I get no hints as
to which setting needs to be increased to improve performance. I have no
chance to see if my FSM settings are too low other than to run vacuum
full verbose in psql, pipe the result to a text file and grep for some
words to get a somewhat comprehensive idea of how much unused space
there is in my system.
Don't get me wrong - I really like PostgreSQL and it works well in my
application. But somehow I feel that it might run much better ...
about the FSM: You say that increasing the FSM is fairly cheap - how
should I know that?
>> did you read my post? In the first part I explained why I don't want
>> to increase the FSM that much.
>
> No, you didn't. You explained *that* you thought you didn't want to
> increase the FSM. You didn't explain why.
>
> FSM expansion comes fairly cheap ...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mlriess@gmx.de
Subject: Re: Autovacuum / full vacuum
In-Reply-To: <dqj07o$2tl4$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox