Hi pgsql-performance,
I was doing mass insertions on my desktop machine and getting at most
1 MB/s disk writes (apart from occasional bursts of 16MB). Inserting 1
million rows with a single integer (data+index 56 MB total) took over
2 MINUTES! The only tuning I had done was shared_buffers=256MB.
Marti Raudsepp wrote:
Unless fdatasync is unsafe, I'd very much want to see it as the
default for 9.1 on Linux (I don't know about other platforms). I
can't see any reasons why each write would need to be sync-ed if I
don't commit that often. Increasing wal_buffers probably has the same
effect
On Sunday 31 October 2010 20:59:31 Greg Smith wrote:
Writes only are sync'd out when you do a commit, or the database does a
checkpoint.
Hm? WAL is written out to disk after an the space provided by wal_buffers(def
8) * XLOG_BLCKSZ (def 8192) is used. The default is 64kb which you reach
On Sun, Oct 31, 2010 at 21:59, Greg Smith g...@2ndquadrant.com wrote:
open_datasync support was just added to Linux itself very recently.
Oh I didn't realize it was a new feature. Indeed O_DSYNC support was
added in 2.6.33
It seems like bad behavior on PostgreSQL's part to default to new,
On 01/11/10 08:59, Greg Smith wrote:
Marti Raudsepp wrote:
Unless fdatasync is unsafe, I'd very much want to see it as the
default for 9.1 on Linux (I don't know about other platforms). I
can't see any reasons why each write would need to be sync-ed if I
don't commit that often. Increasing
