| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Steve Poe <spoe(at)sfnet(dot)cc>, "Nurlan Mukhanov (AL/EKZ)" <Nurlan(dot)Mukhanov(at)ericsson(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgresql works too slow |
| Date: | 2005-04-18 06:40:53 |
| Message-ID: | 42635675.2020309@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice pgsql-performance |
>>Try enabliing your checkpoint_segments. In my example, our database
>>restore took 75mins. After enabling checkpoints_segments to 20, we cut
>>it down to less than 30 minutes.
>
>
> Increasing maintenance_work_mem might help too ... or several other
> settings ... with no information about exactly *what* is slow, it's
> hard to say.
Try turning fsync = false for the duration of your reload.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | brew | 2005-04-18 06:47:37 | Re: Storing Large Objects |
| Previous Message | Tom Lane | 2005-04-18 06:18:40 | Re: Storing Large Objects |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | brew | 2005-04-18 06:47:37 | Re: Storing Large Objects |
| Previous Message | Tom Lane | 2005-04-18 06:18:40 | Re: Storing Large Objects |