Performance: fsync vs. commit delay - Mailing list pgsql-general

From Ilja Golshtein
Subject Performance: fsync vs. commit delay
Date
Msg-id 4538999A.000003.18652@colgate.yandex.ru
Whole thread Raw
List pgsql-general
Hello!

I run an [almost] OLTP system with PG as backend on Windows and on Linux.

The idea is obvious - increase performance as much as possible keeping reliability in mind and I'd highly appreciate
anyhints. 

Some questions about performance/reliability trade.

My first idea was to increase commit_delay having fsync on, since I believed commit_delay is rather conservative thing.
Readingdocs I realized it is actually not, because it prevents server from immediate writes. It means if I disable
fsynconly OS/hardware crashes are dangerous, while after setting nonzero commit_delay PG server crashes are harmful as
well.

Is my understanding correct?

What I want is to do write always but do fsync, say, every 100 ms. Is it possible to control fsyncs and writes
separately,e.g. have write for every commit and fsync as often as specified time range? 

--
Best regards
Ilja Golshtein

pgsql-general by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: Re: plpgsql FOUND bug when SELECT INTO assigns a NULL
Next
From: Andreas Seltenreich
Date:
Subject: Re: why not kill -9 postmaster