| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Julien Drouard <jdrouard(at)ankama(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: pg_toast size |
| Date: | 2006-04-18 21:34:44 |
| Message-ID: | 20060418213443.GJ49405@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-04-18 21:52:38 | Re: merge>hash>loop |
| Previous Message | Jim C. Nasby | 2006-04-18 21:10:05 | Re: Inserts optimization? |