mirror of
https://github.com/postgres/postgres.git
synced 2025-12-22 17:42:17 +03:00
doc: Improve some markups and some wording around archiving modules
This commit adds or fixes markups used in a couple of places in the docs (for <command>, <systemitem> and <literal>). While on it, this clarifies some of the documentation added recently for archiving modules with archive_command, that would still be used as default choice if no external module is defined (though an archive module could as well use an archive_command). Author: Maxim Yablokov Discussion: https://postgr.es/m/b47ec4e8-6f6a-2aba-038e-d5db150b245e@postgrespro.ru Backpatch-through: 15
This commit is contained in:
@@ -121,7 +121,7 @@ ALTER PUBLICATION <replaceable class="parameter">name</replaceable> RENAME TO <r
|
||||
with different column lists is not supported. So, changing the column
|
||||
lists of the tables being subscribed could cause inconsistency of column
|
||||
lists among publications, in which case <command>ALTER PUBLICATION</command>
|
||||
will be successful but later the WalSender on the publisher or the
|
||||
will be successful but later the walsender on the publisher or the
|
||||
subscriber may throw an error. In this scenario, the user needs to
|
||||
recreate the subscription after adjusting the column list or drop the
|
||||
problematic publication using
|
||||
|
||||
@@ -101,9 +101,7 @@ PostgreSQL documentation
|
||||
<listitem>
|
||||
<para>
|
||||
All WAL records required for the backup must contain sufficient full-page writes,
|
||||
which requires you to enable <varname>full_page_writes</varname> on the primary and
|
||||
not to use a tool in your <varname>archive_library</varname> to remove
|
||||
full-page writes from WAL files.
|
||||
which requires you to enable <varname>full_page_writes</varname> on the primary.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
@@ -4658,10 +4658,10 @@ testdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%# '
|
||||
and SQL object names in many (by no means all) contexts. For example,
|
||||
at the start of a command, typing <literal>ins</literal> and pressing
|
||||
TAB will fill in <literal>insert into </literal>. Then, typing a few
|
||||
characters of a table or schema name and pressing TAB will fill in the
|
||||
unfinished name, or offer a menu of possible completions when there's
|
||||
more than one. (Depending on the library in use, you may need to
|
||||
press TAB more than once to get a menu.)
|
||||
characters of a table or schema name and pressing <literal>TAB</literal>
|
||||
will fill in the unfinished name, or offer a menu of possible completions
|
||||
when there's more than one. (Depending on the library in use, you may need to
|
||||
press <literal>TAB</literal> more than once to get a menu.)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -4690,7 +4690,7 @@ $endif
|
||||
of <application>psql</application>. This prevents tab completion,
|
||||
use or recording of command line history, and editing of multi-line
|
||||
commands. It is particularly useful when you need to copy-and-paste
|
||||
text that contains TAB characters.
|
||||
text that contains <literal>TAB</literal> characters.
|
||||
</para>
|
||||
</refsect3>
|
||||
</refsect2>
|
||||
|
||||
Reference in New Issue
Block a user