Fix some spelling errors in the documentation

Author: Daniel Gustafsson <daniel@yesql.se>
This commit is contained in:
Magnus Hagander 2018-11-02 13:55:57 +01:00
parent fbec7459aa
commit 0083a82433
3 changed files with 5 additions and 5 deletions

View File

@ -8478,7 +8478,7 @@ main(int argc, char **argv)
exit_nicely(conn);
}
/* Set always-secure search path, so malicous users can't take control. */
/* Set always-secure search path, so malicious users can't take control. */
res = PQexec(conn,
"SELECT pg_catalog.set_config('search_path', '', false)");
if (PQresultStatus(res) != PGRES_TUPLES_OK)
@ -8648,7 +8648,7 @@ main(int argc, char **argv)
exit_nicely(conn);
}
/* Set always-secure search path, so malicous users can't take control. */
/* Set always-secure search path, so malicious users can't take control. */
res = PQexec(conn,
"SELECT pg_catalog.set_config('search_path', '', false)");
if (PQresultStatus(res) != PGRES_TUPLES_OK)
@ -8875,7 +8875,7 @@ main(int argc, char **argv)
exit_nicely(conn);
}
/* Set always-secure search path, so malicous users can't take control. */
/* Set always-secure search path, so malicious users can't take control. */
res = PQexec(conn, "SET search_path = testlibpq3");
if (PQresultStatus(res) != PGRES_COMMAND_OK)
{

View File

@ -933,7 +933,7 @@ main(int argc, char **argv)
exit_nicely(conn);
}
/* Set always-secure search path, so malicous users can't take control. */
/* Set always-secure search path, so malicious users can't take control. */
res = PQexec(conn,
"SELECT pg_catalog.set_config('search_path', '', false)");
if (PQresultStatus(res) != PGRES_TUPLES_OK)

View File

@ -377,7 +377,7 @@
some care must be taken when truncating groups of tables connected by
foreign keys. When replicating a truncate action, the subscriber will
truncate the same group of tables that was truncated on the publisher,
either explictly specified or implicitly collected via
either explicitly specified or implicitly collected via
<literal>CASCADE</literal>, minus tables that are not part of the
subscription. This will work correctly if all affected tables are part
of the same subscription. But if some tables to be truncated on the