pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedLowercase the replication status in the document
2+ messages / 2 participants
[nested] [flat]
* Lowercase the replication status in the document
@ 2011-08-31 09:11 Fujii Masao <masao.fujii@gmail.com>
2011-08-31 09:39 ` Re: Lowercase the replication status in the document Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
0 siblings, 1 reply; 2+ messages in thread
From: Fujii Masao @ 2011-08-31 09:11 UTC (permalink / raw)
To: pgsql-docs
Hi,
Bruce lowercased the replication status in pg_stat_replication before.
But the status in the document are still in uppercase. We should lowercase
them, too. Patch attached.
http://archives.postgresql.org/pgsql-committers/2011-04/msg00342.php
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachments:
lowercase_status_label_v1.patch (text/x-patch, 1.8K) download
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 67e722f..4b35169 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2103,7 +2103,7 @@ SET ENABLE_SEQSCAN TO OFF;
this standby server confirms receipt of their data.
The synchronous standby will be the first standby named in this list
that is both currently connected and streaming data in real-time
- (as shown by a state of <literal>STREAMING</literal> in the
+ (as shown by a state of <literal>streaming</literal> in the
<link linkend="monitoring-stats-views-table">
<literal>pg_stat_replication</></link> view).
Other standby servers appearing later in this list represent potential
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index c168030..8bcdc07 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1088,14 +1088,14 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
<para>
When a standby first attaches to the primary, it will not yet be properly
- synchronized. This is described as <literal>CATCHUP</> mode. Once
+ synchronized. This is described as <literal>catchup</> mode. Once
the lag between standby and primary reaches zero for the first time
- we move to real-time <literal>STREAMING</> state.
+ we move to real-time <literal>streaming</> state.
The catch-up duration may be long immediately after the standby has
been created. If the standby is shut down, then the catch-up period
will increase according to the length of time the standby has been down.
The standby is only able to become a synchronous standby
- once it has reached <literal>STREAMING</> state.
+ once it has reached <literal>streaming</> state.
</para>
<para>
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Lowercase the replication status in the document
2011-08-31 09:11 Lowercase the replication status in the document Fujii Masao <masao.fujii@gmail.com>
@ 2011-08-31 09:39 ` Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
0 siblings, 0 replies; 2+ messages in thread
From: Heikki Linnakangas @ 2011-08-31 09:39 UTC (permalink / raw)
To: Fujii Masao <masao.fujii@gmail.com>; +Cc: pgsql-docs
On 31.08.2011 12:11, Fujii Masao wrote:
> Bruce lowercased the replication status in pg_stat_replication before.
> But the status in the document are still in uppercase. We should lowercase
> them, too. Patch attached.
> http://archives.postgresql.org/pgsql-committers/2011-04/msg00342.php
Thanks, applied!
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2011-08-31 09:39 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-08-31 09:11 Lowercase the replication status in the document Fujii Masao <masao.fujii@gmail.com>
2011-08-31 09:39 ` Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox