| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Andrew McMillan <andrew(at)catalyst(dot)net(dot)nz>, huang yaqin <hyq(at)gthome(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: good pc but bad performance,why? |
| Date: | 2004-04-08 01:33:34 |
| Message-ID: | 200404080133.i381XYu13325@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > scott.marlowe wrote:
> >>> There is no real need (or benefit) from having the database on a
> >>> journalled filesystem - the journalling is only trying to give similar
> >>> sorts of guarantees to what the fsync in PostgreSQL is doing.
> >>
> >> Is this true? I was under the impression that without at least meta-data
> >> journaling postgresql could still be corrupted by power failure.
>
> > It is false. ext2 isn't crash-safe, and PostgreSQL needs an intact file
> > system for WAL recovery.
>
> But it should be okay to set the filesystem to journal only its own
> metadata. There's no need for it to journal file contents.
Can you set ext2 to journal metadata? I didn't know it could do that.
--
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 | Tom Lane | 2004-04-08 02:13:34 | Re: good pc but bad performance,why? |
| Previous Message | Tom Lane | 2004-04-08 01:31:18 | Re: good pc but bad performance,why? |