Hannu Krosing <hannu(at)skype(dot)net> writes:
> making one of WAL files (strategies) be /dev/null would almost get us
> non-logged writes, except for a little overhead in write() calls.
> fsync() on /dev/null should be instantaneous .
No, you really do want to push it up to a higher level than that.
The CPU and contention costs of generating a WAL record are nontrivial,
and doing so only to throw it away is pretty silly. What's more,
pointing WAL at /dev/null would disable logging for the entire database
cluster, not just selected tables which is what people seem to be
asking for in this thread. (No, I don't wish to deal with multiple
WAL output streams...)
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Aftab Alam||Date: 2005-12-28 03:22:41|
|Subject: sending mail from Postgres|
|Previous:||From: Andrew Dunstan||Date: 2005-12-27 23:57:01|
|Subject: Re: [PATCHES] default resource limits|