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
Changing table-level options requires being a superuser or having the privileges
of the default role pg_read_server_files (to use a filename) or
- the default role pg_execute_server_programs (to use a program),
+ the default role pg_execute_server_program (to use a program),
for security reasons: only certain users should be able to control which file is
read or which program is run. In principle regular users could be allowed to
change the other options, but that's not supported at present.
optional parameter. The return value is NULL when the
log format requested is not a configured
. The
- pg_current_logfiles reflects the contents of the
+ pg_current_logfile reflects the contents of the
current_logfiles file.
char *PQencryptPassword(const char *passwd, const char *user);
PQencryptPassword is an older, deprecated version of
- PQencryptPasswodConn. The difference is that
+ PQencryptPasswordConn. The difference is that
PQencryptPassword does not
require a connection object, and md5 is always used as the
encryption algorithm.
When dumping logical replication subscriptions,
pg_dump will generate
CREATE
- SUBSCRIPTION commands that use the NOCONNECT
+ SUBSCRIPTION commands that use the connect = false
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";