On Wed, May 9, 2012 at 7:29 AM, Bruce Momjian <br...@momjian.us> wrote: > Let me point out that our documentation says nothing about it being > written to the kernel --- it just says "has received the commit record > of the transaction to memory."
Maybe remote_receive would be better. If we're actually writing it back to the kernel before acknowledging the commit, that seems like an implementation defect more than anything else, since it does not - AFAICS - provide any additional, useful guarantee. Another thing I've been wondering is whether, perhaps, we ought to keep synchronous_commit tri-valued: on/local/off, and have a separate GUC for synchronous_replication_mode. It's a bit arbitrary that "on" happens to mean remote fsync rather than remote write/receive. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
