Heikki Linnakangas ad458cfe81 Don't use O_DIRECT when writing WAL files if archiving or streaming is ... enabled. Bypassing the kernel cache is counter-productive in that case, because the archiver/walsender process will read from the WAL file soon after it's written, and if it's not cached the read will cause a physical read, eating I/O bandwidth available on the WAL drive. Also, walreceiver process does unaligned writes, so disable O_DIRECT in walreceiver process for that reason too.		2010-02-19 10:51:04 +00:00
..
walreceiver.h	Don't use O_DIRECT when writing WAL files if archiving or streaming is	2010-02-19 10:51:04 +00:00
walsender.h	Introduce Streaming Replication.	2010-01-15 09:19:10 +00:00