Re: Adding in docs the meaning of pg_stat_replication.sync_state - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Adding in docs the meaning of pg_stat_replication.sync_state
Date
Msg-id CAB7nPqQtSqCH0axmki8JF4XJR6o7stxOGMg2dV5mJOrgK4tqgA@mail.gmail.com
Whole thread Raw
In response to Re: Adding in docs the meaning of pg_stat_replication.sync_state  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Adding in docs the meaning of pg_stat_replication.sync_state  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Thu, Nov 10, 2016 at 10:35 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Wed, Nov 9, 2016 at 2:33 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> Hi all,
>>
>> The documentation does not explain at all what means "sync" or "async"
>> on pg_stat_replication.
>
> "potential" state also should be explained?

Of course.

>> The paragraph "Planning for high availability"
>> mentions "catchup" and "streaming", but it does not say that users can
>> refer to it directly in pg_stat_replication.
>>
>> Thoughts about the patch attached to add a couple of sentences in
>> "Planning for high availability"? We could as well mention it directly
>> in the page of pg_stat_replication but this information seems more
>> suited if located in the HA section.
>
> Yeah, I think it's better to mention them even in pg_stat_replication page.

OK, so I have done things this way. What do you think? At the same
time it would be good to mention all the possible field values in
"state", aka streaming, catchup, etc so I added that as well.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Rushabh Lathia
Date:
Subject: Re: Gather Merge
Next
From: 余森彬
Date:
Subject: Why PostgreSQL doesn't implement a semi sync replication?