Hi,
Just to be curious, why is wal_writer_delay limited to 10s?
I am using postgresql in an embedded environment where every 10s
sensor values are logged and even with "synchronous_commit = off" and
wal_writer_delay=10000 this burns quite a lot of nand cycles. For me
it wouldn't hurt loosing minutes of data - it is only important that
the database is in a consistent state after power loss.
Thanks, Clemens
PS: It is really impressive how flexible and powerful postgresql is.
I am using it on small TP-Link OpenWRT router (32m ram, 400mhz MIPS),
on a raspberry pi as well as on larger servers for "real" database
stuff with huge Hibernate-generated queries. Whenever/weherever I use
postgresql, it does an excellent job and is rock-solid.
Thanks a lot for this impressive piece of work :)
