On Mon, 18 Feb 2008, Tobias Brox wrote:
We actually have some postgres databases that are read-only, others that
can be rebuilt by a script or from some old backup, and yet others that
can be wiped completely without ill effects ... and others where we
would prefer to keep all the data, but it
On Tue, Feb 19, 2008 at 02:48:55PM +, Matthew wrote:
If there's not much write traffic, the WAL won't be used much anyway.
You still have checkpoints.
If you really don't care much about the integrity, then the best option is
probably to put the WAL on ramfs.
Um, that will cause the
Hi,
I want to disable Write Ahead Log (WAL) completely because
of following reasons,
1. I am running Linux on the Compact Flash, which has limited
memory; I can't afford disk space of 32MB for pg_xlog folder. (
checkpoints_segments = 1)
2. CF has own limitation with
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
]
Sent: Monday, February 18, 2008 2:50 PM
To: Kathirvel, Jeevanandam
Cc: pgsql-performance@postgresql.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
On Mon, Feb 18, 2008 at 03:00:47PM +0530, Kathirvel, Jeevanandam wrote:
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?
it will, but in case you'll lost power you
am Mon, dem 18.02.2008, um 14:41:50 +0530 mailte Kathirvel, Jeevanandam
folgendes:
Hi,
I want to disable Write Ahead Log (WAL) completely because of
Please give your inputs, to resolve this issue..
Change the destination for this log to /dev/null
Andreas
--
Andreas
On Feb 18, 2008, at 3:32 AM, hubert depesz lubaczewski wrote:
On Mon, Feb 18, 2008 at 03:00:47PM +0530, Kathirvel, Jeevanandam
wrote:
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.
[Erik Jones]
Right. Without the xlog directory you'll have very little chance of
ever doing any kind of clean stop/start of your database. If you
don't need the reliability offered by Postgres's use of transaction
logs you'll probably be much better served with a different database
