On Tue, Feb 16, 2016 at 7:10 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Given this, I'm on board with just removing the weasel-wording about > timer resolution, except maybe for commit_delay where useful values > are small enough that it's a hazard on old systems.
+1, but I'd move the guidance for commit_delay's effective resolution from "29.4. WAL Configuration" to where commit_delay is introduced, "18.5. Write Ahead Log". -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
