I read the doc before I submit the bug
2014=C4=EA9=D4=C229=C8=D5 4:03 PM=D3=DA "Michael Paquier" <michael.paquier@=
gmail.com>=D0=B4=B5=C0=A3=BA
>
>
>
> On Mon, Sep 29, 2014 at 4:45 PM, <amutu@amutu.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-SYN=
CHRONOUS-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
