Re: Changing "Hot Standby" to "hot standby"
>Looks the same as v5 for me, that applies the same consistency rules >everywhere in the docs. So applied this one. Thank you, Michael
Re: Changing "Hot Standby" to "hot standby"
On Thu, Mar 10, 2022 at 05:58:05PM -0500, Robert Treat wrote: > Not sure why the previous emails didn't go through, and still doesn't > look like they were picked up. In the interest of progress though, > attaching an updated patch with some minor wordsmithing; lmk if you'd > prefer this differently Looks the same as v5 for me, that applies the same consistency rules everywhere in the docs. So applied this one. -- Michael signature.asc Description: PGP signature
Re: Changing "Hot Standby" to "hot standby"
On Thu, Mar 10, 2022 at 8:45 AM Daniel Westermann (DWE) wrote: > > >>>Hmm. Outside the title that had better use upper-case characters for > >>>the first letter of each word, I can see references to the pattern you > >>>are trying to eliminate in amcheck.sgml (1), config.sgml (3), > >>>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as > >>>well if the point is to make the full set of docs consistent? > > >>>As of the full tree, I can see that: > >>> > >>$ git grep "hot standby" | wc -l > >>259 > > >>$ git grep "Hot Standby" | wc -l > >>73 > > >>>So there is a trend for one of the two. > > >>Thanks for looking at it. Yes, I am aware there are other places which > >>would need to be changed and I think I mentioned that in an >>earlier > >>Email. Are you suggesting to change all at once? I wanted to start with the > >>documentation and then continue with the other >>places. > > >Attached a new version which also modifies amcheck.sgml, config.sgml, > >protocol.sgml, and mvcc.sgml accordingly. > > Regards > Daniel > > > From: Daniel Westermann (DWE) > Sent: Wednesday, March 9, 2022 15:15 > To: Michael Paquier > Cc: Robert Treat ; Kyotaro Horiguchi > ; aleksan...@timescale.com > ; pgsql-hackers@lists.postgresql.org > > Subject: Re: Changing "Hot Standby" to "hot standby" > > >>Hmm. Outside the title that had better use upper-case characters for > >>the first letter of each word, I can see references to the pattern you > >>are trying to eliminate in amcheck.sgml (1), config.sgml (3), > >>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as > >>well if the point is to make the full set of docs consistent? > > >>As of the full tree, I can see that: > >> > >>$ git grep "hot standby" | wc -l > >>259 > > >>$ git grep "Hot Standby" | wc -l > >>73 > > >>So there is a trend for one of the two. > > >>Thanks for looking at it. Yes, I am aware there are other places which > >>would need to be changed and I think I mentioned that in an >>earlier > >>Email. Are you suggesting to change all at once? I wanted to start with the > >>documentation and then continue with the other >>places. > > >Attached a new version which also modifies amcheck.sgml, config.sgml, > >protocol.sgml, and mvcc.sgml accordingly. > > Sending this again as my last two mails did not seem to reach the archives or > the commitfest. Or do they need moderation somehow? > Not sure why the previous emails didn't go through, and still doesn't look like they were picked up. In the interest of progress though, attaching an updated patch with some minor wordsmithing; lmk if you'd prefer this differently Robert Treat https://xzilla.net align_hot_standby_v6-rt.patch Description: Binary data
Re: Changing "Hot Standby" to "hot standby"
>>>Hmm. Outside the title that had better use upper-case characters for >>>the first letter of each word, I can see references to the pattern you >>>are trying to eliminate in amcheck.sgml (1), config.sgml (3), >>>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as >>>well if the point is to make the full set of docs consistent? >>>As of the full tree, I can see that: >>> >>$ git grep "hot standby" | wc -l >>259 >>$ git grep "Hot Standby" | wc -l >>73 >>>So there is a trend for one of the two. >>Thanks for looking at it. Yes, I am aware there are other places which would >>need to be changed and I think I mentioned that in an >>earlier Email. Are >>you suggesting to change all at once? I wanted to start with the >>documentation and then continue with the other >>places. >Attached a new version which also modifies amcheck.sgml, config.sgml, >protocol.sgml, and mvcc.sgml accordingly. Regards Daniel From: Daniel Westermann (DWE) Sent: Wednesday, March 9, 2022 15:15 To: Michael Paquier Cc: Robert Treat ; Kyotaro Horiguchi ; aleksan...@timescale.com ; pgsql-hackers@lists.postgresql.org Subject: Re: Changing "Hot Standby" to "hot standby" >>Hmm. Outside the title that had better use upper-case characters for >>the first letter of each word, I can see references to the pattern you >>are trying to eliminate in amcheck.sgml (1), config.sgml (3), >>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as >>well if the point is to make the full set of docs consistent? >>As of the full tree, I can see that: >> >>$ git grep "hot standby" | wc -l >>259 >>$ git grep "Hot Standby" | wc -l >>73 >>So there is a trend for one of the two. >>Thanks for looking at it. Yes, I am aware there are other places which would >>need to be changed and I think I mentioned that in an >>earlier Email. Are >>you suggesting to change all at once? I wanted to start with the >>documentation and then continue with the other >>places. >Attached a new version which also modifies amcheck.sgml, config.sgml, >protocol.sgml, and mvcc.sgml accordingly. Sending this again as my last two mails did not seem to reach the archives or the commitfest. Or do they need moderation somehow? Regards Danieldiff --git a/doc/src/sgml/amcheck.sgml b/doc/src/sgml/amcheck.sgml index 11d1eb5af2..5d61a33936 100644 --- a/doc/src/sgml/amcheck.sgml +++ b/doc/src/sgml/amcheck.sgml @@ -174,7 +174,7 @@ ORDER BY c.relpages DESC LIMIT 10; hypothetically, undiscovered bugs in the underlying B-Tree index access method code. Note that bt_index_parent_check cannot be used when - Hot Standby mode is enabled (i.e., on read-only physical + hot standby mode is enabled (i.e., on read-only physical replicas), unlike bt_index_check. diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 7ed8c82a9d..e2db2a789f 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -4550,7 +4550,7 @@ ANY num_sync ( . @@ -4582,7 +4582,7 @@ ANY num_sync ( . @@ -10887,7 +10887,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' Enables logging of recovery-related debugging output that otherwise would not be logged. This parameter allows the user to override the normal setting of , but only for -specific messages. This is intended for use in debugging Hot Standby. +specific messages. This is intended for use in debugging hot standby. Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, and LOG. The default, LOG, does not affect diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b5b6042104..81fa26f985 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -548,8 +548,8 @@ protocol to make nodes agree on a serializable transactional order. rollforward will take considerably longer, so that technique only offers a solution for disaster recovery, not high availability. A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for - more information. + it is called a hot standby server. See +for more information. @@ -1032,7 +1032,7 @@ primary_slot_name = 'node_a_slot' -Hot Standby feedback propagates upstream, whatever the cascaded arrangement. +Hot standby feedback propagates upstream, whatever the cascaded arrangement. @@ -1499,16 +1499,16 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' Hot Standby - Hot Standby + hot standby -Hot Sta
Re: Changing "Hot Standby" to "hot standby"
>>Hmm. Outside the title that had better use upper-case characters for >>the first letter of each word, I can see references to the pattern you >>are trying to eliminate in amcheck.sgml (1), config.sgml (3), >>protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as >>well if the point is to make the full set of docs consistent? >>As of the full tree, I can see that: >> >>$ git grep "hot standby" | wc -l >>259 >>$ git grep "Hot Standby" | wc -l >>73 >>So there is a trend for one of the two. >Thanks for looking at it. Yes, I am aware there are other places which would >need to be changed and I think I mentioned that in an >earlier Email. Are you >suggesting to change all at once? I wanted to start with the documentation and >then continue with the other >places. Attached a new version which also modifies amcheck.sgml, config.sgml, protocol.sgml, and mvcc.sgml accordingly. Regards Danieldiff --git a/doc/src/sgml/amcheck.sgml b/doc/src/sgml/amcheck.sgml index 11d1eb5af2..5d61a33936 100644 --- a/doc/src/sgml/amcheck.sgml +++ b/doc/src/sgml/amcheck.sgml @@ -174,7 +174,7 @@ ORDER BY c.relpages DESC LIMIT 10; hypothetically, undiscovered bugs in the underlying B-Tree index access method code. Note that bt_index_parent_check cannot be used when - Hot Standby mode is enabled (i.e., on read-only physical + hot standby mode is enabled (i.e., on read-only physical replicas), unlike bt_index_check. diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 7ed8c82a9d..e2db2a789f 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -4550,7 +4550,7 @@ ANY num_sync ( . @@ -4582,7 +4582,7 @@ ANY num_sync ( . @@ -10887,7 +10887,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' Enables logging of recovery-related debugging output that otherwise would not be logged. This parameter allows the user to override the normal setting of , but only for -specific messages. This is intended for use in debugging Hot Standby. +specific messages. This is intended for use in debugging hot standby. Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, and LOG. The default, LOG, does not affect diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b5b6042104..81fa26f985 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -548,8 +548,8 @@ protocol to make nodes agree on a serializable transactional order. rollforward will take considerably longer, so that technique only offers a solution for disaster recovery, not high availability. A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for - more information. + it is called a hot standby server. See +for more information. @@ -1032,7 +1032,7 @@ primary_slot_name = 'node_a_slot' -Hot Standby feedback propagates upstream, whatever the cascaded arrangement. +Hot standby feedback propagates upstream, whatever the cascaded arrangement. @@ -1499,16 +1499,16 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' Hot Standby - Hot Standby + hot standby -Hot Standby is the term used to describe the ability to connect to +Hot standby is the term used to describe the ability to connect to the server and run read-only queries while the server is in archive recovery or standby mode. This is useful both for replication purposes and for restoring a backup to a desired state with great precision. -The term Hot Standby also refers to the ability of the server to move +The term hot standby also refers to the ability of the server to move from recovery through to normal operation while users continue running queries and/or keep their connections open. @@ -1623,7 +1623,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' being executed during recovery. This restriction applies even to temporary tables, because table rows cannot be read or written without assigning a transaction ID, which is currently not possible in a - Hot Standby environment. + hot standby environment. @@ -1703,7 +1703,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' In normal operation, read-only transactions are allowed to use LISTEN and NOTIFY, -so Hot Standby sessions operate under slightly tighter +so hot standby sessions operate under slightly tighter restrictions than ordinary read-only sessions. It is possible that some of these restrictions might be loosened in a future release. @@ -1746,7 +1746,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' -There are also additional types of conflict that can occur with Hot Standby. +There are
Re: Changing "Hot Standby" to "hot standby"
Hi Michael, >On Wed, Mar 09, 2022 at 07:45:32AM +, Daniel Westermann (DWE) wrote: >> Thanks for having a look. Done that way. >Hmm. Outside the title that had better use upper-case characters for >the first letter of each word, I can see references to the pattern you >are trying to eliminate in amcheck.sgml (1), config.sgml (3), >protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as >well if the point is to make the full set of docs consistent? >As of the full tree, I can see that: > >$ git grep "hot standby" | wc -l >259 >$ git grep "Hot Standby" | wc -l >73 >So there is a trend for one of the two. Thanks for looking at it. Yes, I am aware there are other places which would need to be changed and I think I mentioned that in an earlier Email. Are you suggesting to change all at once? I wanted to start with the documentation and then continue with the other places. Regards Daniel
Re: Changing "Hot Standby" to "hot standby"
On Wed, Mar 09, 2022 at 07:45:32AM +, Daniel Westermann (DWE) wrote: > Thanks for having a look. Done that way. Hmm. Outside the title that had better use upper-case characters for the first letter of each word, I can see references to the pattern you are trying to eliminate in amcheck.sgml (1), config.sgml (3), protocol.sgml (3) and mvcc.sgml (1). Shouldn't you refresh these as well if the point is to make the full set of docs consistent? As of the full tree, I can see that: $ git grep "hot standby" | wc -l 259 $ git grep "Hot Standby" | wc -l 73 So there is a trend for one of the two. -- Michael signature.asc Description: PGP signature
Re: Changing "Hot Standby" to "hot standby"
>I think one more small change... > A standby server can also be used for read-only queries, in which case >- it is called a Hot Standby server. See for >+ it is called a hot standby server. See for > more information. > A standby server can also be used for read-only queries, in which case >- it is called a Hot Standby server. See for >+ it is called a hot standby server. See > for > more information. Thanks for having a look. Done that way. Regards Daniel diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b5b6042104..81fa26f985 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -548,8 +548,8 @@ protocol to make nodes agree on a serializable transactional order. rollforward will take considerably longer, so that technique only offers a solution for disaster recovery, not high availability. A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for - more information. + it is called a hot standby server. See +for more information. @@ -1032,7 +1032,7 @@ primary_slot_name = 'node_a_slot' -Hot Standby feedback propagates upstream, whatever the cascaded arrangement. +Hot standby feedback propagates upstream, whatever the cascaded arrangement. @@ -1499,16 +1499,16 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' Hot Standby - Hot Standby + hot standby -Hot Standby is the term used to describe the ability to connect to +Hot standby is the term used to describe the ability to connect to the server and run read-only queries while the server is in archive recovery or standby mode. This is useful both for replication purposes and for restoring a backup to a desired state with great precision. -The term Hot Standby also refers to the ability of the server to move +The term hot standby also refers to the ability of the server to move from recovery through to normal operation while users continue running queries and/or keep their connections open. @@ -1623,7 +1623,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' being executed during recovery. This restriction applies even to temporary tables, because table rows cannot be read or written without assigning a transaction ID, which is currently not possible in a - Hot Standby environment. + hot standby environment. @@ -1703,7 +1703,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' In normal operation, read-only transactions are allowed to use LISTEN and NOTIFY, -so Hot Standby sessions operate under slightly tighter +so hot standby sessions operate under slightly tighter restrictions than ordinary read-only sessions. It is possible that some of these restrictions might be loosened in a future release. @@ -1746,7 +1746,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' -There are also additional types of conflict that can occur with Hot Standby. +There are also additional types of conflict that can occur with hot standby. These conflicts are hard conflicts in the sense that queries might need to be canceled and, in some cases, sessions disconnected to resolve them. The user is provided with several ways to handle these @@ -1947,8 +1947,8 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' If hot_standby is on in postgresql.conf (the default value) and there is a standby.signalstandby.signalfor hot standby -file present, the server will run in Hot Standby mode. -However, it may take some time for Hot Standby connections to be allowed, +file present, the server will run in hot standby mode. +However, it may take some time for hot standby connections to be allowed, because the server will not accept connections until it has completed sufficient recovery to provide a consistent state against which queries can run. During this period, @@ -2282,7 +2282,7 @@ HINT: You can then restart the server after making the necessary configuration Caveats -There are several limitations of Hot Standby. +There are several limitations of hot standby. These can and probably will be fixed in future releases: @@ -2299,7 +2299,7 @@ HINT: You can then restart the server after making the necessary configuration Valid starting points for standby queries are generated at each checkpoint on the primary. If the standby is shut down while the primary - is in a shutdown state, it might not be possible to re-enter Hot Standby + is in a shutdown state, it might not be possible to re-enter hot standby until the primary is started up, so that it generates further starting points in the WAL logs. This situation isn't a problem in the most
Re: Changing "Hot Standby" to "hot standby"
On Mon, Mar 7, 2022 at 11:06 AM Daniel Westermann (DWE) wrote: > > >>> Thanks for having a look. Are you suggesting to change it like this? > >>> -Hot Standby is the term used to describe the ability to connect to > >>> +Hot standby is the term used to describe the ability to connect to > > >>Yes. Isn't it the right form of a sentence? > > I've created and entry in the Commitfest 2022-07 for this. > I think one more small change... A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for + it is called a hot standby server. See for more information. A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for + it is called a hot standby server. See for more information. Robert Treat https://xzilla.net
Re: Changing "Hot Standby" to "hot standby"
>>> Thanks for having a look. Are you suggesting to change it like this? >>> -Hot Standby is the term used to describe the ability to connect to >>> +Hot standby is the term used to describe the ability to connect to >>Yes. Isn't it the right form of a sentence? I've created and entry in the Commitfest 2022-07 for this. Regards Daniel
Re: Changing "Hot Standby" to "hot standby"
>> Thanks for having a look. Are you suggesting to change it like this? >> - Hot Standby is the term used to describe the ability to connect to >> + Hot standby is the term used to describe the ability to connect to >Yes. Isn't it the right form of a sentence? Done like that. Regards Danieldiff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b5b6042104..ea10fe2be8 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -548,7 +548,7 @@ protocol to make nodes agree on a serializable transactional order. rollforward will take considerably longer, so that technique only offers a solution for disaster recovery, not high availability. A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for + it is called a hot standby server. See for more information. @@ -1032,7 +1032,7 @@ primary_slot_name = 'node_a_slot' -Hot Standby feedback propagates upstream, whatever the cascaded arrangement. +Hot standby feedback propagates upstream, whatever the cascaded arrangement. @@ -1499,16 +1499,16 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' Hot Standby - Hot Standby + hot standby -Hot Standby is the term used to describe the ability to connect to +Hot standby is the term used to describe the ability to connect to the server and run read-only queries while the server is in archive recovery or standby mode. This is useful both for replication purposes and for restoring a backup to a desired state with great precision. -The term Hot Standby also refers to the ability of the server to move +The term hot standby also refers to the ability of the server to move from recovery through to normal operation while users continue running queries and/or keep their connections open. @@ -1623,7 +1623,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' being executed during recovery. This restriction applies even to temporary tables, because table rows cannot be read or written without assigning a transaction ID, which is currently not possible in a - Hot Standby environment. + hot standby environment. @@ -1703,7 +1703,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' In normal operation, read-only transactions are allowed to use LISTEN and NOTIFY, -so Hot Standby sessions operate under slightly tighter +so hot standby sessions operate under slightly tighter restrictions than ordinary read-only sessions. It is possible that some of these restrictions might be loosened in a future release. @@ -1746,7 +1746,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' -There are also additional types of conflict that can occur with Hot Standby. +There are also additional types of conflict that can occur with hot standby. These conflicts are hard conflicts in the sense that queries might need to be canceled and, in some cases, sessions disconnected to resolve them. The user is provided with several ways to handle these @@ -1947,8 +1947,8 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' If hot_standby is on in postgresql.conf (the default value) and there is a standby.signalstandby.signalfor hot standby -file present, the server will run in Hot Standby mode. -However, it may take some time for Hot Standby connections to be allowed, +file present, the server will run in hot standby mode. +However, it may take some time for hot standby connections to be allowed, because the server will not accept connections until it has completed sufficient recovery to provide a consistent state against which queries can run. During this period, @@ -2282,7 +2282,7 @@ HINT: You can then restart the server after making the necessary configuration Caveats -There are several limitations of Hot Standby. +There are several limitations of hot standby. These can and probably will be fixed in future releases: @@ -2299,7 +2299,7 @@ HINT: You can then restart the server after making the necessary configuration Valid starting points for standby queries are generated at each checkpoint on the primary. If the standby is shut down while the primary - is in a shutdown state, it might not be possible to re-enter Hot Standby + is in a shutdown state, it might not be possible to re-enter hot standby until the primary is started up, so that it generates further starting points in the WAL logs. This situation isn't a problem in the most common situations where it might happen. Generally, if the primary is
Re: Changing "Hot Standby" to "hot standby"
At Thu, 3 Mar 2022 06:55:43 +, "Daniel Westermann (DWE)" wrote in > Hi Kyotaro, > > >> > >>- Hot Standby is the term used to describe the ability to connect to > >>+ hot standby is the term used to describe the ability to connect to > > >They look like decapitalizing the first word in a sentsnce. > > Thanks for having a look. Are you suggesting to change it like this? > -Hot Standby is the term used to describe the ability to connect to > +Hot standby is the term used to describe the ability to connect to Yes. Isn't it the right form of a sentence? regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Re: Changing "Hot Standby" to "hot standby"
Hi Kyotaro, >> >>- Hot Standby is the term used to describe the ability to connect to >>+ hot standby is the term used to describe the ability to connect to >They look like decapitalizing the first word in a sentsnce. Thanks for having a look. Are you suggesting to change it like this? -Hot Standby is the term used to describe the ability to connect to +Hot standby is the term used to describe the ability to connect to Regards Daniel
Re: Changing "Hot Standby" to "hot standby"
At Wed, 2 Mar 2022 15:22:44 +, "Daniel Westermann (DWE)" wrote in > > Pretty sure that for titles we should keep English capitalization rules. > > Done like that. Thanks for taking a look. -Hot Standby feedback propagates upstream, whatever the cascaded arrangement. +hot standby feedback propagates upstream, whatever the cascaded arrangement -Hot Standby is the term used to describe the ability to connect to +hot standby is the term used to describe the ability to connect to They look like decapitalizing the first word in a sentsnce. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Re: Changing "Hot Standby" to "hot standby"
Hi Aleksander, > Pretty sure that for titles we should keep English capitalization rules. Done like that. Thanks for taking a look. Regards Danieldiff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index b5b6042104..08eb1ad946 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -548,7 +548,7 @@ protocol to make nodes agree on a serializable transactional order. rollforward will take considerably longer, so that technique only offers a solution for disaster recovery, not high availability. A standby server can also be used for read-only queries, in which case - it is called a Hot Standby server. See for + it is called a hot standby server. See for more information. @@ -1032,7 +1032,7 @@ primary_slot_name = 'node_a_slot' -Hot Standby feedback propagates upstream, whatever the cascaded arrangement. +hot standby feedback propagates upstream, whatever the cascaded arrangement. @@ -1499,16 +1499,16 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' Hot Standby - Hot Standby + hot standby -Hot Standby is the term used to describe the ability to connect to +hot standby is the term used to describe the ability to connect to the server and run read-only queries while the server is in archive recovery or standby mode. This is useful both for replication purposes and for restoring a backup to a desired state with great precision. -The term Hot Standby also refers to the ability of the server to move +The term hot standby also refers to the ability of the server to move from recovery through to normal operation while users continue running queries and/or keep their connections open. @@ -1623,7 +1623,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' being executed during recovery. This restriction applies even to temporary tables, because table rows cannot be read or written without assigning a transaction ID, which is currently not possible in a - Hot Standby environment. + hot standby environment. @@ -1703,7 +1703,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' In normal operation, read-only transactions are allowed to use LISTEN and NOTIFY, -so Hot Standby sessions operate under slightly tighter +so hot standby sessions operate under slightly tighter restrictions than ordinary read-only sessions. It is possible that some of these restrictions might be loosened in a future release. @@ -1746,7 +1746,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' -There are also additional types of conflict that can occur with Hot Standby. +There are also additional types of conflict that can occur with hot standby. These conflicts are hard conflicts in the sense that queries might need to be canceled and, in some cases, sessions disconnected to resolve them. The user is provided with several ways to handle these @@ -1947,8 +1947,8 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)' If hot_standby is on in postgresql.conf (the default value) and there is a standby.signalstandby.signalfor hot standby -file present, the server will run in Hot Standby mode. -However, it may take some time for Hot Standby connections to be allowed, +file present, the server will run in hot standby mode. +However, it may take some time for hot standby connections to be allowed, because the server will not accept connections until it has completed sufficient recovery to provide a consistent state against which queries can run. During this period, @@ -2282,7 +2282,7 @@ HINT: You can then restart the server after making the necessary configuration Caveats -There are several limitations of Hot Standby. +There are several limitations of hot standby. These can and probably will be fixed in future releases: @@ -2299,7 +2299,7 @@ HINT: You can then restart the server after making the necessary configuration Valid starting points for standby queries are generated at each checkpoint on the primary. If the standby is shut down while the primary - is in a shutdown state, it might not be possible to re-enter Hot Standby + is in a shutdown state, it might not be possible to re-enter hot standby until the primary is started up, so that it generates further starting points in the WAL logs. This situation isn't a problem in the most common situations where it might happen. Generally, if the primary is
Re: Changing "Hot Standby" to "hot standby"
Hi Daniel, > Here is a patch that changes "Hot Standby" to "hot standby" in high-availability.sgml, so we have a consistent wording. > Thoughts? ``` - Hot Standby Parameter Reference + hot standby Parameter Reference ``` Pretty sure that for titles we should keep English capitalization rules. -- Best regards, Aleksander Alekseev
