| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(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-10 13:35:14 |
| Message-ID: | CAHGQGwG54uS81AHwUyxJYnkLazHc=_iecLP7vKSBqsdW_B8-SQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
> 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.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-11-10 13:49:55 | switching documentation build to XSLT |
| Previous Message | Emre Hasegeli | 2016-11-10 12:41:19 | Re: Floating point comparison inconsistencies of the geometric types |