Re: Adding in docs the meaning of pg_stat_replication.sync_state

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Adding in docs the meaning of pg_stat_replication.sync_state
Date: 2016-11-11 13:03:53
Message-ID: CAB7nPqQtSqCH0axmki8JF4XJR6o7stxOGMg2dV5mJOrgK4tqgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 10, 2016 at 10:35 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Nov 9, 2016 at 2:33 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)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 Content-Type Size
sync-state-docs.patch binary/octet-stream 2.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2016-11-11 14:02:05 Re: Do we need use more meaningful variables to replace 0 in catalog head files?
Previous Message Rushabh Lathia 2016-11-11 12:58:02 Re: Gather Merge