From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> |
Cc: | lec <limec(at)streamyx(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dump / restore for optimization? |
Date: | 2004-07-01 15:04:03 |
Message-ID: | 27386.1088694243@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Shridhar Daithankar <shridhar(at)frodo(dot)hserus(dot)net> writes:
> lec wrote:
>> I always have to dump & restore to make a database (which is in use for
>> a few months) efficient again. I have scheduled nightly vacuum analyze,
>> but only dump & restore can make the database efficient again. Has
>> anyone experience this?
> You could try several things if you want to avoid dump/restore
> - Try vacuum full instead of vacuum analyze
> - Postgresql versions pre-7.4 had index bloat with vacuum. 7.4.x fixed this. So
> try with that.
> - Run autovacuum daemon if possible.
The most likely bet is that he needs larger FSM settings in
postgresql.conf. I'd try larger FSM and more frequent regular
vacuums, rather than vacuum full. (autovacuum is good but
not necessary.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Gearon | 2004-07-01 15:21:56 | Re: backups |
Previous Message | Bill Montgomery | 2004-07-01 15:02:06 | Re: Dump / restore for optimization? |