From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Perfomance Tuning |
Date: | 2003-08-11 22:16:44 |
Message-ID: | 200308112216.h7BMGiF06162@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
scott.marlowe wrote:
> On Fri, 8 Aug 2003, Andrew Sullivan wrote:
>
> > On Fri, Aug 08, 2003 at 09:40:20AM -0700, Jonathan Gardner wrote:
> > >
> > > Redhat puts ext3 on by default. Consider switching to a non-journaling FS
> > > (ext2?) with the partition that holds your data and WAL.
> >
> > I would give you exactly the opposite advice: _never_ use a
> > non-journalling fs for your data and WAL. I suppose if you can
> > afford to lose some transactions, you can do without journalling.
> > Otherwise, you're just borrowing trouble, near as I can tell.
>
> I'd argue that a reliable filesystem (ext2) is still better than a
> questionable journaling filesystem (ext3 on kernels <2.4.20).
>
> This isn't saying to not use jounraling, but I would definitely test it
> under load first to make sure it's not gonna lose data or get corrupted.
That _would_ work if ext2 was a reliable file system --- it is not.
This is the problem of Linux file systems --- they have unreliable, and
journalled, with nothing in between, except using a journalling file
system and having it only journal metadata.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2003-08-11 22:42:28 | Re: Odd problem with performance in duplicate database |
Previous Message | Josh Berkus | 2003-08-11 22:03:46 | Re: Odd problem with performance in duplicate database |