From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
---|---|
To: | "Greg Stark" <gsstark(at)mit(dot)edu>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Opteron scaling with PostgreSQL |
Date: | 2004-06-12 07:34:27 |
Message-ID: | 54798A299E68514AB7C4DEBA25F03BE101BA2E@postal.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Greg Stark
> Sent: Saturday, June 12, 2004 12:18 AM
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Opteron scaling with PostgreSQL
>
>
>
> Steve Wolfe <nw(at)codon(dot)com> writes:
>
> > I've run with fsync off on my production servers for
> years. Power
> > never goes off, and RAID 5 protects me from disk failures.
> Sooner or
> > later, it may bite me in the butt. We make backups
> sufficiently often
> > that the small amount of data we'll lose will be far offset by the
> > tremendous performance boost that we've enjoyed. In fact, we even
> > have a backup server sitting there doing nothing, which can
> take over
> > the duties of the main DB server within a VERY short amount of time.
>
> That's good, because you'll eventually need it.
>
> All it will take will be a Linux crash for the database files
> on disk to become corrupted. No amount of UPS or RAID
> protection will protect from that.
Another important point is that the data in an organization is always
more valuable than the hardware and the software.
Hose up the hardware and the software, and insurance gets new stuff.
Hose up the data and you are really hosed for good.
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Seymour | 2004-06-12 11:19:05 | Re: Opteron scaling with PostgreSQL |
Previous Message | Greg Stark | 2004-06-12 07:18:08 | Re: Opteron scaling with PostgreSQL |