Files
postgresql/doc/src/sgml
Alvaro Herrera 961cab0a5a Allow "in place" tablespaces.
This is a backpatch to branches 10-14 of the following commits:

7170f2159fb2 Allow "in place" tablespaces.
c6f2f01611d4 Fix pg_basebackup with in-place tablespaces.
f6f0db4d6240 Fix pg_tablespace_location() with in-place tablespaces
7a7cd84893e0 doc: Remove mention to in-place tablespaces for pg_tablespace_location()
5344723755bd Remove unnecessary Windows-specific basebackup code.

In-place tablespaces were introduced as a testing helper mechanism, but
they are going to be used for a bugfix in WAL replay to be backpatched
to all stable branches.

I (Álvaro) had to adjust some code to account for lack of
get_dirent_type() in branches prior to 14.

Author: Thomas Munro <thomas.munro@gmail.com>
Author: Michaël Paquier <michael@paquier.xyz>
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Discussion: https://postgr.es/m/20220722081858.omhn2in5zt3g4nek@alvherre.pgsql
2022-07-27 07:55:13 +02:00
..
2021-11-24 18:34:30 +02:00
2020-07-05 15:37:57 +02:00
2021-07-16 12:39:23 +02:00
2020-10-26 19:17:05 -04:00
2021-09-29 11:56:36 +09:00
2021-09-29 11:56:36 +09:00
2020-02-26 13:05:30 -08:00
2020-03-29 11:15:11 +02:00
2022-07-27 07:55:13 +02:00
2021-01-29 14:09:41 +13:00
2019-09-08 10:27:29 +02:00
2020-07-18 22:43:35 +09:00
2021-04-07 13:52:26 +02:00
2020-10-19 13:48:00 +02:00
2020-06-07 13:18:36 +02:00
2021-07-05 09:38:17 +05:30
2020-07-18 22:43:35 +09:00
2021-07-05 09:38:17 +05:30
2019-10-25 20:39:41 +02:00
2021-07-16 12:39:23 +02:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2022-01-07 19:04:56 -05:00
2021-09-19 11:36:53 -04:00
2021-07-16 12:39:23 +02:00
2021-01-05 14:26:37 -05:00
2020-08-28 08:19:12 +02:00
2022-07-08 18:36:27 -04:00
2021-07-16 12:39:23 +02:00
2020-12-23 09:33:20 -05:00
2021-07-05 09:38:17 +05:30
2020-06-07 17:16:30 -04:00
2019-09-08 10:27:29 +02:00
2021-09-29 11:56:36 +09:00
2021-07-16 12:39:23 +02:00
2021-12-08 16:54:53 -05: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
	can be embedded inside of <command>, unlike <xref>


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.