These have been found while cross-checking for the use of unique words
in the documentation, and a wait event was not getting generated in a way
consistent to what the documentation provided.
Author: Alexander Lakhin
Discussion: https://postgr.es/m/
9b5a3a85-899a-ae62-dbab-
1e7943aa5ab1@gmail.com
optional parameter. The return value is <literal>NULL</literal> when the
log format requested is not a configured
<xref linkend="guc-log-destination">. The
- <function>pg_current_logfiles</function> reflects the contents of the
+ <function>pg_current_logfile</function> reflects the contents of the
<filename>current_logfiles</> file.
</para>
char *PQencryptPassword(const char *passwd, const char *user);
</synopsis>
<function>PQencryptPassword</> is an older, deprecated version of
- <function>PQencryptPasswodConn</>. The difference is that
+ <function>PQencryptPasswordConn</>. The difference is that
<function>PQencryptPassword</> does not
require a connection object, and <literal>md5</> is always used as the
encryption algorithm.
<para>
When dumping logical replication subscriptions,
<application>pg_dump</application> will generate <command>CREATE
- SUBSCRIPTION</command> commands that use the <literal>NOCONNECT</literal>
+ SUBSCRIPTION</command> commands that use the <literal>connect = false</literal>
option, so that restoring the subscription does not make remote connections
for creating a replication slot or for initial table copy. That way, the
dump can be restored without requiring network access to the remote
event_name = "LockFileCreateSync";
break;
case WAIT_EVENT_LOCK_FILE_CREATE_WRITE:
- event_name = "LockFileCreateWRITE";
+ event_name = "LockFileCreateWrite";
break;
case WAIT_EVENT_LOCK_FILE_RECHECKDATADIR_READ:
event_name = "LockFileReCheckDataDirRead";