diff --git a/doc/src/sgml/acronyms.sgml b/doc/src/sgml/acronyms.sgml index 817d062c7e6..6e64b190ea2 100644 --- a/doc/src/sgml/acronyms.sgml +++ b/doc/src/sgml/acronyms.sgml @@ -634,7 +634,7 @@ Server Name Indication, - RFC 6066 + RFC 6066 diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 096ddab481c..2907079e2a6 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1625,7 +1625,7 @@ SCRAM-SHA-256$<iteration count>:&l where salt, StoredKey and ServerKey are in Base64 encoded format. This format is - the same as that specified by RFC 5803. + the same as that specified by RFC 5803. diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index 55bbb20dacc..daf671e6205 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1702,7 +1702,7 @@ ORDER BY c COLLATE ebcdic; - BCP 47 + BCP 47 @@ -3399,7 +3399,7 @@ RESET client_encoding; - RFC 3629 + RFC 3629 diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 0b7100d9d8d..cf5eb22fc89 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -691,7 +691,7 @@ include_dir directory entire Distinguished Name (DN) of the certificate. This option is probably best used in conjunction with a username map. The comparison is done with the DN in - RFC 2253 + RFC 2253 format. To see the DN of a client certificate in this format, do @@ -1090,7 +1090,7 @@ omicron bryanh guest1 Ident authentication, which relies on an Identification Protocol - (RFC 1413) + (RFC 1413) service on the client's machine. (On local Unix-socket connections, this is treated as peer authentication.) @@ -1229,7 +1229,7 @@ omicron bryanh guest1 The method scram-sha-256 performs SCRAM-SHA-256 authentication, as described in - RFC 7677. It + RFC 7677. It is a challenge-response scheme that prevents password sniffing on untrusted connections and supports storing passwords on the server in a cryptographically hashed form that is thought to be secure. @@ -1336,7 +1336,7 @@ omicron bryanh guest1 GSSAPI is an industry-standard protocol for secure authentication defined in - RFC 2743. + RFC 2743. PostgreSQL supports GSSAPI for authentication, communications encryption, or both. @@ -1651,7 +1651,7 @@ omicron bryanh guest1 The Identification Protocol is described in - RFC 1413. + RFC 1413. Virtually every Unix-like operating system ships with an ident server that listens on TCP port 113 by default. The basic functionality of an ident server @@ -1820,7 +1820,7 @@ omicron bryanh guest1 Set to 1 to make the connection between PostgreSQL and the LDAP server use TLS encryption. This uses the StartTLS - operation per RFC 4513. + operation per RFC 4513. See also the ldapscheme option for an alternative. @@ -1915,7 +1915,7 @@ omicron bryanh guest1 ldapurl - An RFC 4516 + An RFC 4516 LDAP URL. This is an alternative way to write some of the other LDAP options in a more compact and standard form. The format is @@ -1978,7 +1978,7 @@ ldap[s]://host[:port]/OpenLDAP as the LDAP client library, the ldapserver setting may be omitted. In that case, a list of host names and ports is looked up via - RFC 2782 DNS SRV records. + RFC 2782 DNS SRV records. The name _ldap._tcp.DOMAIN is looked up, where DOMAIN is extracted from ldapbasedn. diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 73e51b0b114..6646820d6a0 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -2471,7 +2471,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02' the date and time. PostgreSQL accepts that format on input, but on output it uses a space rather than T, as shown above. This is for readability and for consistency with - RFC 3339 as + RFC 3339 as well as some other database systems. @@ -4367,7 +4367,7 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' ); The data type uuid stores Universally Unique Identifiers - (UUID) as defined by RFC 4122, + (UUID) as defined by RFC 4122, ISO/IEC 9834-8:2005, and related standards. (Some systems refer to this data type as a globally unique identifier, or GUID,GUID instead.) This diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 43082704a7c..b332aa435df 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -3317,7 +3317,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt %z - is replaced by the time zone offset from UTC; a leading plus sign stands for east of UTC, a minus sign for west of UTC, hours and minutes follow with two digits each and no - delimiter between them (common form for RFC 822 date headers). + delimiter between them (common form for RFC 822 date headers). diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index bf13216e477..f017c2ef047 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -4901,7 +4901,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three'); The base64 format is that - of RFC + of RFC 2045 Section 6.8. As per the RFC, encoded lines are broken at 76 characters. However instead of the MIME CRLF end-of-line marker, only a newline is used for end-of-line. @@ -14198,7 +14198,7 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple uuid_extract_version (uuid) smallint This function extracts the version from a UUID of the variant described by - RFC 4122. For + RFC 4122. For other variants, this function returns null. For example, for a UUID generated by gen_random_uuid, this function will return 4. @@ -15537,7 +15537,7 @@ table2-mapping values, with an additional SQL/JSON null value, and composite data structures that use JSON arrays and objects. The model is a formalization of the implied data model in the JSON specification - RFC 7159. + RFC 7159. diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml index 1dbb9606e91..ec0e6bf7425 100644 --- a/doc/src/sgml/json.sgml +++ b/doc/src/sgml/json.sgml @@ -13,7 +13,7 @@ JSON data types are for storing JSON (JavaScript Object Notation) - data, as specified in RFC + data, as specified in RFC 7159. Such data can also be stored as text, but the JSON data types have the advantage of enforcing that each stored value is valid according to the JSON rules. There are also diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 35fb346ed97..9199d0d2e58 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -920,7 +920,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void); connection parameters. There are two accepted formats for these strings: plain keyword/value strings and URIs. URIs generally follow - RFC + RFC 3986, except that multi-host connection strings are allowed as further described below. @@ -1005,7 +1005,7 @@ postgresql:///mydb?host=localhost&port=5433 The connection URI needs to be encoded with percent-encoding + url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding if it includes symbols with special meaning in any of its parts. Here is an example where the equal sign (=) is replaced with %3D and the space character with @@ -9343,7 +9343,7 @@ user=admin LDAP query will be performed. The result must be a list of keyword = value pairs which will be used to set connection options. The URL must conform to - RFC 1959 + RFC 1959 and be of the form ldap://[hostname[:port]]/search_base?attribute?search_scope?filter @@ -9487,7 +9487,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*) For backward compatibility with earlier versions of PostgreSQL, the host IP address is verified in a manner different - from RFC 6125. + from RFC 6125. The host IP address is always matched against dNSName SANs as well as iPAddress SANs, and can be matched against the Common Name attribute if no relevant SANs exist. diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml index 2db159be71c..b8b89696e7f 100644 --- a/doc/src/sgml/pgcrypto.sgml +++ b/doc/src/sgml/pgcrypto.sgml @@ -442,7 +442,7 @@ gen_salt(type text [, iter_count integer ]) returns text The functions here implement the encryption part of the OpenPGP - (RFC 4880) + (RFC 4880) standard. Supported are both symmetric-key and public-key encryption. diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index a8ec72c27f4..aaaf131edd7 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1600,7 +1600,7 @@ SELCT 1/0; respectively. The frontend might close the connection at this point if it is dissatisfied with the response. To continue after G, using the GSSAPI C bindings as discussed in - RFC 2744 + RFC 2744 or equivalent, perform a GSSAPI initialization by calling gss_init_sec_context() in a loop and sending the result to the server, starting with an empty input and then with each @@ -1737,8 +1737,8 @@ SELCT 1/0; The implemented SASL mechanisms at the moment are SCRAM-SHA-256 and its variant with channel binding SCRAM-SHA-256-PLUS. They are described in - detail in RFC 7677 - and RFC 5802. + detail in RFC 7677 + and RFC 5802. diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 539748ffc29..4ad2cb1d991 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -2983,7 +2983,7 @@ lo_import 152801 writes column values separated by commas, applying the quoting rules described in - RFC 4180. + RFC 4180. This output is compatible with the CSV format of the server's COPY command. A header line with column names is generated unless diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml index a7767049c8c..bde5f391e5c 100644 --- a/doc/src/sgml/textsearch.sgml +++ b/doc/src/sgml/textsearch.sgml @@ -2221,7 +2221,7 @@ LIMIT 10; email does not support all valid email characters as - defined by RFC 5322. + defined by RFC 5322. Specifically, the only non-alphanumeric characters supported for email user names are period, dash, and underscore. diff --git a/doc/src/sgml/uuid-ossp.sgml b/doc/src/sgml/uuid-ossp.sgml index 6f851ac85f2..acd20a51f01 100644 --- a/doc/src/sgml/uuid-ossp.sgml +++ b/doc/src/sgml/uuid-ossp.sgml @@ -29,7 +29,7 @@ shows the functions available to generate UUIDs. The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and - RFC 4122 + RFC 4122 specify four algorithms for generating UUIDs, identified by the version numbers 1, 3, 4, and 5. (There is no version 2 algorithm.) Each of these algorithms could be suitable for a different set of