| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | Jason Godden <jasongodden(at)optushome(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Growing Database Size Solved |
| Date: | 2003-06-14 16:59:01 |
| Message-ID: | 8269.1055609941@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> On Sat, Jun 14, 2003 at 18:57:42 +1000,
> Jason Godden <jasongodden(at)optushome(dot)com(dot)au> wrote:
>> My mistake - even though I was running VACUUM everyday I wasn't running VACUUM
>> FULL - a VACUUM FULL fixed the problem. Strange - I thought that regular
>> VACUUM was pretty good these days?
> You need to make sure that FSM is set high enough
The default FSM settings are good for a database of up to maybe 100mb
or so. For your 2Gb database you probably need to ratchet max_fsm_pages
up by about a factor of 10, and make sure that max_fsm_relations is big
enough for all your tables too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-14 17:18:15 | Re: Index not being used in MAX function (7.2.3) |
| Previous Message | Bruno BAGUETTE | 2003-06-14 16:55:36 | RE : full featured alter table? |