| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Adding in docs the meaning of pg_stat_replication.sync_state |
| Date: | 2016-11-09 05:33:17 |
| Message-ID: | CAB7nPqT7APWrvPFZrcjKEHoq4=g3z2ErxtTdojSf+sDALzuemA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
The documentation does not explain at all what means "sync" or "async"
on pg_stat_replication. 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.
Thanks,
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| repstate-info.patch | text/x-diff | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-11-09 05:54:45 | Re: [PATCH] Reload SSL certificates on SIGHUP |
| Previous Message | Michael Paquier | 2016-11-09 05:03:48 | Re: Do we need use more meaningful variables to replace 0 in catalog head files? |