From: Jim C. Nasby <jnasby@pervasive.com>
To: Julien Drouard <jdrouard@ankama.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg_toast size
Date: Tue, 18 Apr 2006 16:34:44 -0500
Message-ID: <20060418213443.GJ49405@pervasive.com> (raw)
In-Reply-To: <000c01c65fc5$41c78a70$0700a8c0@ankama.lan>
References: <000c01c65fc5$41c78a70$0700a8c0@ankama.lan>
On Fri, Apr 14, 2006 at 03:13:43PM +0200, Julien Drouard wrote:
> Hi everyone,
>
> I've seen my pg_toast tables are becoming bigger and bigger. After googling I would like to modify my max_fsm_pages parameter to prevent that kind of problem. So I'm wondering if changing this parameter is enough and after that how can I reduce the size of these tables? By doing a full vacuum?
A full vacuum would do it. CLUSTERing the table might rewrite the toast
tables as well.
As for toast, if you do a vacuum verbose over the entire cluster, it
will tell you at the end how much space you need in the FSM. See also
http://www.pervasivepostgres.com/instantkb13/article.aspx?id=10087
and http://www.pervasivepostgres.com/instantkb13/article.aspx?id=10116
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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: jnasby@pervasive.com, jdrouard@ankama.com
Subject: Re: pg_toast size
In-Reply-To: <20060418213443.GJ49405@pervasive.com>
* 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