<term><literal>USER SET</literal></term>
<listitem>
<para>
- Specifies that variable should be set on behalf of ordinary role.
- That lets non-superuser and non-replication role to set placeholder
- variables, with permission requirements is not known yet;
+ Specifies that the variable should be set on behalf of an ordinary role.
+ That allows non-superuser and non-replication roles to set placeholder
+ variables, whose permission requirements are not known yet;
see <xref linkend="runtime-config-custom"/>. The variable won't
be set if it appears to require superuser privileges.
</para>
<term><literal>USER SET</literal></term>
<listitem>
<para>
- Specifies that variable should be set on behalf of ordinary role.
- That lets non-superuser and non-replication role to set placeholder
- variables, with permission requirements is not known yet;
+ Specifies that the variable should be set on behalf of an ordinary role.
+ That allows non-superuser and non-replication roles to set placeholder
+ variables, whose permission requirements are not known yet;
see <xref linkend="runtime-config-custom"/>. The variable won't
be set if it appears to require superuser privileges.
</para>
</para>
<para>
- Since <productname>PostgreSQL</productname> 16 the output includes
- column with the values of
+ Since <productname>PostgreSQL</productname> 16, the output includes a
+ column with the values of the
<link linkend="sql-alterrole-user-set"><literal>USER SET</literal></link>
flag for each setting.
</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
<structfield>objid</structfield> column.
</para>
/*
* 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
* was reached.
*/
* to the connected client.
*
* We don't buffer the information about all memory contexts in a
- * backend into StringInfo and log it as one message. Otherwise which
- * may require the buffer to be enlarged very much and lead to OOM
- * error since there can be a large number of memory contexts in a
- * backend. Instead, we log one message per memory context.
+ * backend into StringInfo and log it as one message. That would
+ * require the buffer to be enlarged, risking an OOM as there could
+ * be a large number of memory contexts in a backend. Instead, we
+ * log one message per memory context.
*/
ereport(LOG_SERVER_ONLY,
(errhidestmt(true),
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.
*/
const char *error = PQresultErrorMessage(result);
bbb
(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();
load_test_pg_db_role_setting
------------------------------
SHOW test_pg_db_role_setting.superuser_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();
SHOW test_pg_db_role_setting.superuser_param;