Re: Perfomance Tuning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Perfomance Tuning
Date: 2003-08-08 20:13:47
Message-ID: 29638.1060373627@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Rod Taylor wrote:
>> On Fri, 2003-08-08 at 14:53, Andrew Sullivan wrote:
>>> 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.
>>
>> Agreed.. WAL cannot recover something when WAL no longer exists due to a
>> filesystem corruption.

> It is true that ext2 isn't good because the file system may not recover,
> but BSD UFS isn't a journalled file system, but does guarantee file
> system recovery after a crash --- it is especially good using soft
> updates.

The main point here is that the filesystem has to be able to take care
of itself; we expect it not to lose any files or forget where the data
is. If it wants to use journalling to accomplish that, fine.

Journalling file contents updates, as opposed to filesystem metadata,
should be redundant with what we do in WAL. So I'd recommend
journalling metadata only, if that option is available (and if Postgres
stuff is the only stuff on the disk...)

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message elein 2003-08-11 03:04:40 Windows on SuSE? 7.4
Previous Message Andrew Sullivan 2003-08-08 19:56:58 Re: Perfomance Tuning