Fix typos in code and comments

Author: Justin Pryzby
Discussion: https://postgr.es/m/20230110045722.GD9837@telsasoft.com
This commit is contained in:
Michael Paquier 2023-01-11 15:16:38 +09:00
parent 69fb29d1af
commit 5f6401f81c
9 changed files with 17 additions and 17 deletions

View File

@ -211,9 +211,9 @@ ALTER DATABASE <replaceable class="parameter">name</replaceable> RESET ALL
<term><literal>USER SET</literal></term> <term><literal>USER SET</literal></term>
<listitem> <listitem>
<para> <para>
Specifies that variable should be set on behalf of ordinary role. Specifies that the variable should be set on behalf of an ordinary role.
That lets non-superuser and non-replication role to set placeholder That allows non-superuser and non-replication roles to set placeholder
variables, with permission requirements is not known yet; variables, whose permission requirements are not known yet;
see <xref linkend="runtime-config-custom"/>. The variable won't see <xref linkend="runtime-config-custom"/>. The variable won't
be set if it appears to require superuser privileges. be set if it appears to require superuser privileges.
</para> </para>

View File

@ -241,9 +241,9 @@ ALTER ROLE { <replaceable class="parameter">role_specification</replaceable> | A
<term><literal>USER SET</literal></term> <term><literal>USER SET</literal></term>
<listitem> <listitem>
<para> <para>
Specifies that variable should be set on behalf of ordinary role. Specifies that the variable should be set on behalf of an ordinary role.
That lets non-superuser and non-replication role to set placeholder That allows non-superuser and non-replication roles to set placeholder
variables, with permission requirements is not known yet; variables, whose permission requirements are not known yet;
see <xref linkend="runtime-config-custom"/>. The variable won't see <xref linkend="runtime-config-custom"/>. The variable won't
be set if it appears to require superuser privileges. be set if it appears to require superuser privileges.
</para> </para>

View File

@ -1901,8 +1901,8 @@ INSERT INTO tbl1 VALUES ($1, $2) \bind 'first value' 'second value' \g
</para> </para>
<para> <para>
Since <productname>PostgreSQL</productname> 16 the output includes Since <productname>PostgreSQL</productname> 16, the output includes a
column with the values of column with the values of the
<link linkend="sql-alterrole-user-set"><literal>USER SET</literal></link> <link linkend="sql-alterrole-user-set"><literal>USER SET</literal></link>
flag for each setting. flag for each setting.
</para> </para>

View File

@ -1580,7 +1580,7 @@
</para> </para>
<para> <para>
A specualtive insertion lock consists of a transaction ID and a speculative A speculative insertion lock consists of a transaction ID and a speculative
insertion token. The speculative insertion token is displayed in the insertion token. The speculative insertion token is displayed in the
<structfield>objid</structfield> column. <structfield>objid</structfield> column.
</para> </para>

View File

@ -2114,7 +2114,7 @@ CheckRecoveryConsistency(void)
/* /*
* Check that pg_tblspc doesn't contain any real directories. Replay * Check that pg_tblspc doesn't contain any real directories. Replay
* of Database/CREATE_* records may have created ficticious tablespace * of Database/CREATE_* records may have created fictitious tablespace
* directories that should have been removed by the time consistency * directories that should have been removed by the time consistency
* was reached. * was reached.
*/ */

View File

@ -717,10 +717,10 @@ MemoryContextStatsDetail(MemoryContext context, int max_children,
* to the connected client. * to the connected client.
* *
* We don't buffer the information about all memory contexts in a * We don't buffer the information about all memory contexts in a
* backend into StringInfo and log it as one message. Otherwise which * backend into StringInfo and log it as one message. That would
* may require the buffer to be enlarged very much and lead to OOM * require the buffer to be enlarged, risking an OOM as there could
* error since there can be a large number of memory contexts in a * be a large number of memory contexts in a backend. Instead, we
* backend. Instead, we log one message per memory context. * log one message per memory context.
*/ */
ereport(LOG_SERVER_ONLY, ereport(LOG_SERVER_ONLY,
(errhidestmt(true), (errhidestmt(true),

View File

@ -1447,7 +1447,7 @@ ExecQueryAndProcessResults(const char *query,
if (!AcceptResult(result, false)) if (!AcceptResult(result, false))
{ {
/* /*
* Some error occured, either a server-side failure or a failure * Some error occurred, either a server-side failure or a failure
* to submit the command string. Record that. * to submit the command string. Record that.
*/ */
const char *error = PQresultErrorMessage(result); const char *error = PQresultErrorMessage(result);

View File

@ -122,7 +122,7 @@ SHOW test_pg_db_role_setting.user_param;
bbb bbb
(1 row) (1 row)
-- module is loaded, and placeholder values are succesfully set -- module is loaded, and placeholder values are successfully set
SELECT load_test_pg_db_role_setting(); SELECT load_test_pg_db_role_setting();
load_test_pg_db_role_setting load_test_pg_db_role_setting
------------------------------ ------------------------------

View File

@ -56,7 +56,7 @@ ALTER ROLE regress_regular_user SET test_pg_db_role_setting.superuser_param = 'c
SHOW test_pg_db_role_setting.superuser_param; SHOW test_pg_db_role_setting.superuser_param;
SHOW test_pg_db_role_setting.user_param; SHOW test_pg_db_role_setting.user_param;
-- module is loaded, and placeholder values are succesfully set -- module is loaded, and placeholder values are successfully set
SELECT load_test_pg_db_role_setting(); SELECT load_test_pg_db_role_setting();
SHOW test_pg_db_role_setting.superuser_param; SHOW test_pg_db_role_setting.superuser_param;