Consistently use the IETF HTML links instead of a random mix of
different sites and formats. This also fixes one broken link for JSON
documentation.
JSON data types are for storing JSON (JavaScript Object Notation)
- data, as specified in
://rfc7159.net/rfc7159">RFC
+ data, as specified in
s://tools.ietf.org/html/rfc7159">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
Several
libpq> functions parse a user-specified string to obtain
connection parameters. There are two accepted formats for these strings:
plain keyword = value strings
- and
://www.ietf.org/rfc/rfc3986.txt">RFC
+ and
s://tools.ietf.org/html/rfc3986">RFC
3986 URIs.
-
://www.ietf.org/rfc/rfc4880.txt">
+
s://tools.ietf.org/html/rfc4880">
-
://www.ietf.org/rfc/rfc1321.txt">
+
s://tools.ietf.org/html/rfc1321">
The MD5 Message-Digest Algorithm.
-
://www.ietf.org/rfc/rfc2104.txt">
+
s://tools.ietf.org/html/rfc2104">
HMAC: Keyed-Hashing for Message Authentication.