diff options
author | Bruce Momjian | 2019-04-11 17:25:34 +0000 |
---|---|---|
committer | Bruce Momjian | 2019-04-11 17:25:34 +0000 |
commit | c4dfe5718f661b18c68485e1faecf1b0b10dbaca (patch) | |
tree | d08b91a3199d592d9a9a5f106562682b34a3db56 | |
parent | 62d4953956197a76e070fef9f315878f1d58bb29 (diff) |
doc: adjust libpq wording to be neither/nor
Reported-by: postgresql@cohi.at
Discussion: https://postgr.es/m/155419437926.737.10876947446993402227@wrigleys.postgresql.org
Backpatch-through: 9.4
-rw-r--r-- | doc/src/sgml/libpq.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 05f58ca83b0..b3beb575cee 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -3768,7 +3768,7 @@ char *PQescapeLiteral(PGconn *conn, const char *str, size_t length); </tip> <para> - Note that it is not necessary nor correct to do escaping when a data + Note that it is neither necessary nor correct to do escaping when a data value is passed as a separate parameter in <function>PQexecParams</> or its sibling routines. </para> |