| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
| Cc: | Bealach-na Bo <bealach_na_bo(at)hotmail(dot)com>, ahodgson(at)simkin(dot)ca, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Why so slow? |
| Date: | 2006-05-02 20:17:41 |
| Message-ID: | 20060502201740.GB97354@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, Apr 30, 2006 at 10:03:46AM -0400, Bill Moran wrote:
> At this point, it seems like you need to do 2 things:
> 1) Schedule lazy vacuum to run, or configure autovacuum.
> 2) Schedule some downtime to run "vacuum full" to recover some disk space.
>
> #2 only needs done once to get you back on track, assuming that #1 is
> done properly.
You'll also want to reindex since vacuum full won't clean the indexes
up. You might also want to read
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 | Bruno Wolff III | 2006-05-02 20:19:29 | Re: postgresql transaction id monitoring with nagios |
| Previous Message | Jim C. Nasby | 2006-05-02 20:13:35 | Re: Why so slow? |