From: | "Kathirvel, Jeevanandam" <Jeevanandam(dot)Kathirvel(at)honeywell(dot)com> |
---|---|
To: | <depesz(at)depesz(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Disable WAL completely |
Date: | 2008-02-18 09:30:47 |
Message-ID: | EB493C98A0338748AA3D997E071B0574601DED@IE10EV813.global.ds.honeywell.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Depesz,
Is there way to minimize the I/O operation on disk/CF.
Can I create RAM file system and point the pg_xlog files to RAM
location instead of CF. whether this will work?
Regards,
Jeeva
-----Original Message-----
From: hubert depesz lubaczewski [mailto:depesz(at)depesz(dot)com]
Sent: Monday, February 18, 2008 2:50 PM
To: Kathirvel, Jeevanandam
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Disable WAL completely
On Mon, Feb 18, 2008 at 02:41:50PM +0530, Kathirvel, Jeevanandam wrote:
> I want to disable Write Ahead Log (WAL) completely because
> of following reasons,
basically, you can't disable it.
regards,
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly paid DBA. here's my CV!" :)
http://www.depesz.com/ - blog dla ciebie (i moje CV)
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2008-02-18 09:32:40 | Re: Disable WAL completely |
Previous Message | A. Kretschmer | 2008-02-18 09:24:48 | Re: Disable WAL completely |