From: | Jov <amutu(at)amutu(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #11517: the pg_stat_replication.sync_stat show sync when synchronous_commit is set to be off |
Date: | 2014-09-29 09:22:46 |
Message-ID: | CADyrUxPhmx_cKGnd80b7kgHyW_8bcL6z3BqseKR_KyN0KGy7-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I read the doc before I submit the bug
2014年9月29日 4:03 PM于 "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com>写道:
>
>
>
> On Mon, Sep 29, 2014 at 4:45 PM, <amutu(at)amutu(dot)com> wrote:
>>
>> from the doc,when synchronous_commit set to off or local,the commit will
not
>> wait the remote slave reveive data,so it is not asynchronous
replication.but I
>> find the pg_stat_replication wrongly report the sync_stat to sync.This
can
>
> This is not a bug, please refer to the documentation about
synchronous_commit:
>
http://www.postgresql.org/docs/devel/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT
>
> When synchronous_commit is set to off, local or remote_write, the master
node does not wait for the confirmation from the sync standby that the WAL
has been flushed to disk (for remote_write it waits for the write
confirmation), and the standby is still considered as sync, of course if
synchronous_standby_names is set.
I can't figure out this conclusion from the doc above.I appreciate it if
you point me more specifically.
> Regards,
> --
> Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-09-29 14:06:34 | Re: BUG #11457: The below query crashes 9.3.5, but not 9.3.4 |
Previous Message | Michael Paquier | 2014-09-29 08:02:44 | Re: BUG #11517: the pg_stat_replication.sync_stat show sync when synchronous_commit is set to be off |