| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "Decibel!" <decibel(at)decibel(dot)org> |
| Cc: | "Kevin Kempter" <kevin(at)kevinkempterllc(dot)com>, "Pgsql performance" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: significant vacuum issues - looking for suggestions |
| Date: | 2007-08-27 21:56:33 |
| Message-ID: | 46D30240.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>>> Decibel! <decibel(at)decibel(dot)org> 08/27/07 4:00 PM >>>
> > > They're running version 8.1.4
>
> As for your pg_dump idea... why not just do a CREATE TABLE AS SELECT *
> FROM bloated_table? That would likely be much faster than messing around
> with pg_dump.
He wanted to upgrade to 8.2.4. CREATE TABLE AS won't get him there.
> > > They're running version 8.1.4 on 4-way dell boxes
> > > with 4Gig of memory on each box attached to RAID-10 disk arrays.
>
> What kind of disk hardware is this running on? A good raid 10 array with
> write caching should be able to handle a 200G database fairly well
What other details were you looking for?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Kempter | 2007-08-27 22:00:01 | Re: significant vacuum issues - looking for suggestions |
| Previous Message | Merlin Moncure | 2007-08-27 21:18:05 | Re: asynchronous commit feature |