aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/acronyms.sgml2
-rw-r--r--doc/src/sgml/catalogs.sgml2
-rw-r--r--doc/src/sgml/charset.sgml4
-rw-r--r--doc/src/sgml/client-auth.sgml16
-rw-r--r--doc/src/sgml/datatype.sgml4
-rw-r--r--doc/src/sgml/ecpg.sgml2
-rw-r--r--doc/src/sgml/func.sgml4
-rw-r--r--doc/src/sgml/json.sgml2
-rw-r--r--doc/src/sgml/libpq.sgml8
-rw-r--r--doc/src/sgml/pgcrypto.sgml2
-rw-r--r--doc/src/sgml/protocol.sgml6
-rw-r--r--doc/src/sgml/ref/psql-ref.sgml2
-rw-r--r--doc/src/sgml/textsearch.sgml2
-rw-r--r--doc/src/sgml/uuid-ossp.sgml2
14 files changed, 29 insertions, 29 deletions
diff --git a/doc/src/sgml/acronyms.sgml b/doc/src/sgml/acronyms.sgml
index 22e0dc5c70b..137851419d7 100644
--- a/doc/src/sgml/acronyms.sgml
+++ b/doc/src/sgml/acronyms.sgml
@@ -625,7 +625,7 @@
<ulink
url="https://en.wikipedia.org/wiki/Server_Name_Indication">
Server Name Indication</ulink>,
- <ulink url="https://tools.ietf.org/html/rfc6066#section-3">RFC 6066</ulink>
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc6066#section-3">RFC 6066</ulink>
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 4945d4bc6e8..e1d9a67a96d 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1624,7 +1624,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
</synopsis>
where <replaceable>salt</replaceable>, <replaceable>StoredKey</replaceable> and
<replaceable>ServerKey</replaceable> are in Base64 encoded format. This format is
- the same as that specified by <ulink url="https://tools.ietf.org/html/rfc5803">RFC 5803</ulink>.
+ the same as that specified by <ulink url="https://datatracker.ietf.org/doc/html/rfc5803">RFC 5803</ulink>.
</para>
<para>
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 975b9dc9523..9242ba64c36 100644
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -1603,7 +1603,7 @@ ORDER BY c COLLATE ebcdic;
</listitem>
<listitem>
<para>
- <ulink url="https://tools.ietf.org/html/bcp47">BCP 47</ulink>
+ <ulink url="https://www.rfc-editor.org/info/bcp47">BCP 47</ulink>
</para>
</listitem>
<listitem>
@@ -3300,7 +3300,7 @@ RESET client_encoding;
</varlistentry>
<varlistentry>
- <term><ulink url="https://tools.ietf.org/html/rfc3629">RFC 3629</ulink></term>
+ <term><ulink url="https://datatracker.ietf.org/doc/html/rfc3629">RFC 3629</ulink></term>
<listitem>
<para>
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index a36c7b163d4..7db407e8ee5 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -662,7 +662,7 @@ include_dir <replaceable>directory</replaceable>
entire <literal>Distinguished Name (DN)</literal> of the certificate.
This option is probably best used in conjunction with a username map.
The comparison is done with the <literal>DN</literal> in
- <ulink url="https://tools.ietf.org/html/rfc2253">RFC 2253</ulink>
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc2253">RFC 2253</ulink>
format. To see the <literal>DN</literal> of a client certificate
in this format, do
<programlisting>
@@ -1089,7 +1089,7 @@ omicron bryanh guest1
<para>
<link linkend="auth-ident">Ident authentication</link>, which
relies on an <quote>Identification Protocol</quote>
- (<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>)
+ (<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>)
service on the client's machine. (On local Unix-socket connections,
this is treated as peer authentication.)
</para>
@@ -1228,7 +1228,7 @@ omicron bryanh guest1
<para>
The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256
authentication, as described in
- <ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>. It
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>. 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.
@@ -1340,7 +1340,7 @@ omicron bryanh guest1
<para>
<productname>GSSAPI</productname> is an industry-standard protocol
for secure authentication defined in
- <ulink url="https://tools.ietf.org/html/rfc2743">RFC 2743</ulink>.
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc2743">RFC 2743</ulink>.
<productname>PostgreSQL</productname>
supports <productname>GSSAPI</productname> for authentication,
communications encryption, or both.
@@ -1655,7 +1655,7 @@ omicron bryanh guest1
<para>
The <quote>Identification Protocol</quote> is described in
- <ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>.
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>.
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
@@ -1824,7 +1824,7 @@ omicron bryanh guest1
<para>
Set to 1 to make the connection between PostgreSQL and the LDAP server
use TLS encryption. This uses the <literal>StartTLS</literal>
- operation per <ulink url="https://tools.ietf.org/html/rfc4513">RFC 4513</ulink>.
+ operation per <ulink url="https://datatracker.ietf.org/doc/html/rfc4513">RFC 4513</ulink>.
See also the <literal>ldapscheme</literal> option for an alternative.
</para>
</listitem>
@@ -1919,7 +1919,7 @@ omicron bryanh guest1
<term><literal>ldapurl</literal></term>
<listitem>
<para>
- An <ulink url="https://tools.ietf.org/html/rfc4516">RFC 4516</ulink>
+ An <ulink url="https://datatracker.ietf.org/doc/html/rfc4516">RFC 4516</ulink>
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
<synopsis>
@@ -1982,7 +1982,7 @@ ldap[s]://<replaceable>host</replaceable>[:<replaceable>port</replaceable>]/<rep
<productname>OpenLDAP</productname> as the LDAP client library, the
<literal>ldapserver</literal> setting may be omitted. In that case, a
list of host names and ports is looked up via
- <ulink url="https://tools.ietf.org/html/rfc2782">RFC 2782</ulink> DNS SRV records.
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc2782">RFC 2782</ulink> DNS SRV records.
The name <literal>_ldap._tcp.DOMAIN</literal> is looked up, where
<literal>DOMAIN</literal> is extracted from <literal>ldapbasedn</literal>.
</para>
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index a591f79ba71..9e94c5122bf 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. <productname>PostgreSQL</productname> accepts that format on
input, but on output it uses a space rather than <literal>T</literal>, as shown
above. This is for readability and for consistency with
- <ulink url="https://tools.ietf.org/html/rfc3339">RFC 3339</ulink> as
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc3339">RFC 3339</ulink> as
well as some other database systems.
</para>
</note>
@@ -4367,7 +4367,7 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' );
<para>
The data type <type>uuid</type> stores Universally Unique Identifiers
- (UUID) as defined by <ulink url="https://tools.ietf.org/html/rfc4122">RFC 4122</ulink>,
+ (UUID) as defined by <ulink url="https://datatracker.ietf.org/doc/html/rfc4122">RFC 4122</ulink>,
ISO/IEC 9834-8:2005, and related standards.
(Some systems refer to this data type as a globally unique identifier, or
GUID,<indexterm><primary>GUID</primary></indexterm> instead.) This
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 3e3cef6eb25..bb4bccd5a94 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -3316,7 +3316,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<literal>%z</literal> - 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 <ulink url="https://tools.ietf.org/html/rfc822">RFC 822</ulink> date headers).
+ delimiter between them (common form for <ulink url="https://datatracker.ietf.org/doc/html/rfc822">RFC 822</ulink> date headers).
</para>
</listitem>
<listitem>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 758b40abf08..22e5164d7f3 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4783,7 +4783,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
<listitem>
<para>
The <literal>base64</literal> format is that
- of <ulink url="https://tools.ietf.org/html/rfc2045#section-6.8">RFC
+ of <ulink url="https://datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
2045 Section 6.8</ulink>. As per the <acronym>RFC</acronym>, 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.
@@ -15268,7 +15268,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
- <ulink url="https://tools.ietf.org/html/rfc7159">RFC 7159</ulink>.
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc7159">RFC 7159</ulink>.
</para>
<para>
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index b6c2ddbf55a..f51254490c7 100644
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -13,7 +13,7 @@
<para>
JSON data types are for storing JSON (JavaScript Object Notation)
- data, as specified in <ulink url="https://tools.ietf.org/html/rfc7159">RFC
+ data, as specified in <ulink url="https://datatracker.ietf.org/doc/html/rfc7159">RFC
7159</ulink>. Such data can also be stored as <type>text</type>, 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 6fc35bc0c1a..b667fca9f67 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -873,7 +873,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
- <ulink url="https://tools.ietf.org/html/rfc3986">RFC
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc3986">RFC
3986</ulink>, except that multi-host connection strings are allowed
as further described below.
</para>
@@ -958,7 +958,7 @@ postgresql:///mydb?host=localhost&amp;port=5433
<para>
The connection <acronym>URI</acronym> needs to be encoded with <ulink
- url="https://tools.ietf.org/html/rfc3986#section-2.1">percent-encoding</ulink>
+ url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding</ulink>
if it includes symbols with special meaning in any of its parts. Here is
an example where the equal sign (<literal>=</literal>) is replaced with
<literal>%3D</literal> and the space character with
@@ -8561,7 +8561,7 @@ user=admin
LDAP query will be performed. The result must be a list of
<literal>keyword = value</literal> pairs which will be used to set
connection options. The URL must conform to
- <ulink url="https://tools.ietf.org/html/rfc1959">RFC 1959</ulink>
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc1959">RFC 1959</ulink>
and be of the form
<synopsis>
ldap://[<replaceable>hostname</replaceable>[:<replaceable>port</replaceable>]]/<replaceable>search_base</replaceable>?<replaceable>attribute</replaceable>?<replaceable>search_scope</replaceable>?<replaceable>filter</replaceable>
@@ -8705,7 +8705,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
<para>
For backward compatibility with earlier versions of PostgreSQL, the host
IP address is verified in a manner different
- from <ulink url="https://tools.ietf.org/html/rfc6125">RFC 6125</ulink>.
+ from <ulink url="https://datatracker.ietf.org/doc/html/rfc6125">RFC 6125</ulink>.
The host IP address is always matched against <literal>dNSName</literal>
SANs as well as <literal>iPAddress</literal> 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
<para>
The functions here implement the encryption part of the OpenPGP
- (<ulink url="https://tools.ietf.org/html/rfc4880">RFC 4880</ulink>)
+ (<ulink url="https://datatracker.ietf.org/doc/html/rfc4880">RFC 4880</ulink>)
standard. Supported are both symmetric-key and public-key encryption.
</para>
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index c4ff7fcd034..aa14d166535 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1571,7 +1571,7 @@ SELCT 1/0;<!-- this typo is intentional -->
respectively. The frontend might close the connection at this point
if it is dissatisfied with the response. To continue after
<literal>G</literal>, using the GSSAPI C bindings as discussed in
- <ulink url="https://tools.ietf.org/html/rfc2744">RFC 2744</ulink>
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc2744">RFC 2744</ulink>
or equivalent, perform a <acronym>GSSAPI</acronym> initialization by
calling <function>gss_init_sec_context()</function> in a loop and sending
the result to the server, starting with an empty input and then with each
@@ -1708,8 +1708,8 @@ SELCT 1/0;<!-- this typo is intentional -->
The implemented SASL mechanisms at the moment
are <literal>SCRAM-SHA-256</literal> and its variant with channel
binding <literal>SCRAM-SHA-256-PLUS</literal>. They are described in
- detail in <ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>
- and <ulink url="https://tools.ietf.org/html/rfc5802">RFC 5802</ulink>.
+ detail in <ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>
+ and <ulink url="https://datatracker.ietf.org/doc/html/rfc5802">RFC 5802</ulink>.
</para>
<para>
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index b23296e6897..7ff6e1d95d7 100644
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -2983,7 +2983,7 @@ lo_import 152801
</indexterm>
writes column values separated by commas, applying the quoting
rules described in
- <ulink url="https://tools.ietf.org/html/rfc4180">RFC 4180</ulink>.
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc4180">RFC 4180</ulink>.
This output is compatible with the CSV format of the server's
<command>COPY</command> 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;
<para>
<literal>email</literal> does not support all valid email characters as
- defined by <ulink url="https://tools.ietf.org/html/rfc5322">RFC 5322</ulink>.
+ defined by <ulink url="https://datatracker.ietf.org/doc/html/rfc5322">RFC 5322</ulink>.
Specifically, the only non-alphanumeric characters supported for
email user names are period, dash, and underscore.
</para>
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 @@
<xref linkend="uuid-ossp-functions"/> shows the functions available to
generate UUIDs.
The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and
- <ulink url="https://tools.ietf.org/html/rfc4122">RFC 4122</ulink>
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc4122">RFC 4122</ulink>
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
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-19 20:16:44 +0000