rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-09-28 00:21:50 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: Fix some grammar and typos

Browse Source 
This fixes some areas related to logical replication and custom RMGRs.

Author: Ekaterina Kiryanova
Discussion: https://postgr.es/m/fa4773f1-1396-384a-bcd7-85b5e013f399@postgrespro.ru
Backpatch-through: 15
This commit is contained in:
Michael Paquier 2022-10-01 15:28:11 +09:00
parent 2267085c16
commit 64b431d15c
4 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/custom-rmgr.sgml
View File

@ -66,7 +66,7 @@ typedef struct RmgrData
* Register a new custom WAL resource manager.
*
* Resource manager IDs must be globally unique across all extensions. Refer
* to https://wiki.postgresql.org/wiki/CustomWALResourceManager to reserve a
* to https://wiki.postgresql.org/wiki/CustomWALResourceManagers to reserve a
* unique RmgrId for your extension, to avoid conflicts with other extension
* developers. During development, use RM_EXPERIMENTAL_ID to avoid needlessly
* reserving a new ID.
@ -76,8 +76,8 @@ extern void RegisterCustomRmgr(RmgrId rmid, RmgrData *rmgr);
<function>RegisterCustomRmgr</function> must be called from the
extension module's <link linkend="xfunc-c-dynload">_PG_init</link> function.
While developing a new extension, use <literal>RM_EXPERIMENTAL_ID</literal>
for <parameter>rmid</parameter>. When you ready to release the extension to
users, reserve a new resource manager ID at the <ulink
for <parameter>rmid</parameter>. When you are ready to release the extension
to users, reserve a new resource manager ID at the <ulink
url="https://wiki.postgresql.org/wiki/CustomWALResourceManagers">Custom WAL
Resource Manager</ulink> page.
</para>

2
doc/src/sgml/func.sgml
View File

@ -25502,7 +25502,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
will be logged at
<literal>LOG</literal> message level. They will appear in
the server log based on the log configuration set
(See <xref linkend="runtime-config-logging"/> for more information),
(see <xref linkend="runtime-config-logging"/> for more information),
but will not be sent to the client regardless of
<xref linkend="guc-client-min-messages"/>.
</para></entry>

6
doc/src/sgml/logical-replication.sgml
View File

@ -688,18 +688,18 @@ test_sub=# SELECT * FROM t3;
<itemizedlist>
<listitem>
<para>
one of the publications has no row filter.
One of the publications has no row filter.
</para>
</listitem>
<listitem>
<para>
one of the publications was created using <literal>FOR ALL TABLES</literal>.
One of the publications was created using <literal>FOR ALL TABLES</literal>.
This clause does not allow row filters.
</para>
</listitem>
<listitem>
<para>
one of the publications was created using
One of the publications was created using
<literal>FOR TABLES IN SCHEMA</literal> and the table belongs to
the referred schema. This clause does not allow row filters.
</para>

2
src/backend/access/transam/rmgr.c
View File

@ -89,7 +89,7 @@ RmgrNotFound(RmgrId rmid)
* Register a new custom WAL resource manager.
*
* Resource manager IDs must be globally unique across all extensions. Refer
* to https://wiki.postgresql.org/wiki/CustomWALResourceManager to reserve a
* to https://wiki.postgresql.org/wiki/CustomWALResourceManagers to reserve a
* unique RmgrId for your extension, to avoid conflicts with other extension
* developers. During development, use RM_EXPERIMENTAL_ID to avoid needlessly
* reserving a new ID.