Files
postgresql/doc/src/sgml
Tom Lane 622ae4621e Fix assorted issues in backend's GSSAPI encryption support.
Unrecoverable errors detected by GSSAPI encryption can't just be
reported with elog(ERROR) or elog(FATAL), because attempting to
send the error report to the client is likely to lead to infinite
recursion or loss of protocol sync.  Instead make this code do what
the SSL encryption code has long done, which is to just report any
such failure to the server log (with elevel COMMERROR), then pretend
we've lost the connection by returning errno = ECONNRESET.

Along the way, fix confusion about whether message translation is done
by pg_GSS_error() or its callers (the latter should do it), and make
the backend version of that function work more like the frontend
version.

Avoid allocating the port->gss struct until it's needed; we surely
don't need to allocate it in the postmaster.

Improve logging of "connection authorized" messages with GSS enabled.
(As part of this, I back-patched the code changes from dc11f31a1.)

Make BackendStatusShmemSize() account for the GSS-related space that
will be allocated by CreateSharedBackendStatus().  This omission
could possibly cause out-of-shared-memory problems with very high
max_connections settings.

Remove arbitrary, pointless restriction that only GSS authentication
can be used on a GSS-encrypted connection.

Improve documentation; notably, document the fact that libpq now
prefers GSS encryption over SSL encryption if both are possible.

Per report from Mikael Gustavsson.  Back-patch to v12 where
this code was introduced.

Discussion: https://postgr.es/m/e5b0b6ed05764324a2f3fe7acfc766d5@smhi.se
2020-12-28 17:44:17 -05:00
..
2020-07-05 15:37:57 +02:00
2020-09-10 14:15:26 +02:00
2020-11-07 12:26:24 +01:00
2020-10-26 19:17:05 -04:00
2020-02-26 13:05:30 -08:00
2020-03-29 11:15:11 +02:00
2020-11-25 09:49:00 +01:00
2019-09-08 10:27:29 +02:00
2020-12-20 07:20:33 +03:00
2020-10-19 19:28:54 +03:00
2020-11-21 08:26:20 +01:00
2020-07-18 22:43:35 +09:00
2020-12-01 14:36:30 +02:00
2020-12-20 07:20:33 +03:00
2020-10-19 13:48:00 +02:00
2020-06-07 13:18:36 +02:00
2020-07-18 22:43:35 +09:00
2019-10-25 20:39:41 +02:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2020-12-01 14:36:30 +02:00
2020-01-01 12:21:45 -05:00
2019-09-08 10:27:29 +02:00
2020-10-19 19:28:54 +03:00
2020-10-19 19:28:54 +03:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2020-08-28 08:19:12 +02:00
2020-12-23 09:33:20 -05:00
2020-12-23 09:33:20 -05:00
2020-12-23 09:33:20 -05:00
2020-12-23 09:33:20 -05:00
2020-11-19 09:32:47 +01:00
2020-06-07 17:16:30 -04:00
2020-06-07 17:16:30 -04:00
2020-10-19 19:28:54 +03:00
2020-10-19 19:28:54 +03:00
2019-09-08 10:27:29 +02:00
2020-12-23 09:33:20 -05:00
2019-08-13 08:40:17 +02:00
2019-09-08 10:27:29 +02:00

<!-- doc/src/sgml/README.links -->

Linking within DocBook documents can be confusing, so here is a summary:


Intra-document Linking
----------------------

<xref>
	use to get chapter/section number from the title of the target
	link, or xreflabel if defined at the target, or refentrytitle if target
        is a refentry;  has no close tag
	http://www.oasis-open.org/docbook/documentation/reference/html/xref.html

linkend=
	controls the target of the link/xref, required

endterm=
	for <xref>, allows the text of the link/xref to be taken from a
	different link target title

<link>
	use to supply text for the link, only uses linkend, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.html


External Linking
----------------

<ulink>
	like <link>, but uses a URL (not a document target);  requires
	</ulink>; if no text is specified, the URL appears as the link
	text
	http://www.oasis-open.org/docbook/documentation/reference/html/ulink.html

url=
	used by <ulink> to specify the URL, required


Guidelines
----------

- For an internal link, if you want to supply text, use <link>, else
  <xref>.

- Specific nouns like GUC variables, SQL commands, and contrib modules
  usually have xreflabels.

- For an external link, use <ulink>, with or without link text.

- xreflabels added to tags prevent the chapter/section for id's from being
  referenced;  only the xreflabel is accessible.  Therefore, use xreflabels
  only when linking is common, and chapter/section information is unneeded.