| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Jeff <threshar(at)torgo(dot)978(dot)org> |
| Cc: | Marek Florianczyk <franki(at)tpi(dot)pl>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: performance problem - 10.000 databases |
| Date: | 2003-11-06 15:07:57 |
| Message-ID: | Pine.LNX.4.33.0311060806210.12004-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 6 Nov 2003, Jeff wrote:
> On 06 Nov 2003 15:21:03 +0100
> Marek Florianczyk <franki(at)tpi(dot)pl> wrote:
>
>
> > fsync = false
>
> HOLD THE BOAT THERE BATMAN!
>
> I would *STRONGLY* advise not running with fsync=false in production as
> PG _CANNOT_ guaruntee data consistancy in the event of a hardware
> failure. It would sure suck to have a power failure screw up your nice
> db for the users!
Note that if you're on an IDE drive and you haven't disabled the write
cache, you may as well turn off fsync as well, as it's just getting in the
way and doing nothing, i.e. the IDE drives are already lying about fsync
so why bother.
Step the first, get on SCSI / or a good IDE RAID controller, then step the
second, turn fsync back on. Without reliable storage, fsync is a dunsel.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-06 15:17:45 | Re: performance problem - 10.000 databases |
| Previous Message | Tom Lane | 2003-11-06 14:48:49 | Re: Process Files |