On Wed, May 9, 2012 at 7:29 AM, Bruce Momjian <bruce(at)momjian(dot)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.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2012-05-09 13:04:08|
|Subject: Re: age(xid) on hot standby|
|Previous:||From: MauMau||Date: 2012-05-09 12:10:07|
|Subject: Can pg_trgm handle non-alphanumeric characters?|