| From: | Madison Kelly <linux(at)alteeve(dot)com> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, Gary Doades <gpd(at)gpdnet(dot)co(dot)uk>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: DB is slow until DB is reloaded |
| Date: | 2010-01-04 21:57:12 |
| Message-ID: | 4B426438.40109@alteeve.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Steve Crawford wrote:
> Madison Kelly wrote:
>>
>> I wanted to get ahead of the problem, hence my question here. :)
>> I've set this to run at night ('iwt' being the DB in question):
>>
>> su postgres -c "psql iwt -c \"VACUUM ANALYZE VERBOSE\"
>
> And why not the vacuumdb command?:
>
> su postgres -c "vacuumdb --analyze --verbose iwt"
>
>
> But this is duct-tape and bailing-wire. You REALLY need to make sure
> that autovacuum is running - you are likely to have much better results
> with less pain.
>
> Cheers,
> Steve
As for why '-c ...', I guess it was just a matter of which command came
to mind first. :) Is there a particular benefit to using the 'vacuumdb'
wrapper?
As for autovacuum, I assumed (yes, I know) that all v8.x releases
enabled it by default. How would I confirm that it's running or not?
Madi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-04 21:59:25 | Re: forced sequential scan when condition has current_user |
| Previous Message | Madison Kelly | 2010-01-04 21:54:19 | Re: DB is slow until DB is reloaded |