1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-05 23:56:58 +03:00
Thomas Munro 2b1f580ee2 Remove configure probes for symlink/readlink, and dead code.
symlink() and readlink() are in SUSv2 and all targeted Unix systems have
them.  We have partial emulation on Windows.  Code that raised runtime
errors on systems without it has been dead for years, so we can remove
that and also references to such systems in the documentation.

Define HAVE_READLINK and HAVE_SYMLINK macros on Unix.  Our Windows
replacement functions based on junction points can't be used for
relative paths or for non-directories, so the macros can be used to
check for full symlink support.  The places that deal with tablespaces
can just use symlink functions without checking the macros.  (If they
did check the macros, they'd need to provide an #else branch with a
runtime or compile time error, and it'd be dead code.)

Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Reviewed-by: Andres Freund <andres@anarazel.de>
Discussion: https://postgr.es/m/CA+hUKGJ3LHeP9w5Fgzdr4G8AnEtJ=z=p6hGDEm4qYGEUX5B6fQ@mail.gmail.com
2022-08-05 09:22:56 +12:00
..
2022-05-19 09:42:17 +02:00
2022-05-19 09:42:17 +02:00
2022-08-04 16:09:15 +07:00
2021-09-29 11:56:13 +09:00
2022-04-08 00:26:44 -07:00
2022-05-19 09:42:17 +02:00
2022-07-08 14:05:05 +12: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
2022-04-06 23:06:46 -07:00
2020-07-18 22:43:35 +09:00
2022-05-19 09:42:17 +02:00
2020-07-18 22:43:35 +09:00
2020-10-19 19:28:54 +03:00
2022-01-07 19:04:57 -05:00
2021-08-27 18:20:40 +02:00
2020-08-28 08:19:12 +02:00
2022-07-08 18:36:27 -04:00
2022-05-19 09:42:17 +02:00
2022-05-19 09:42:17 +02:00
2022-08-02 19:55:59 +09:00
2022-07-08 14:05:05 +12:00
2022-06-30 11:26:40 -04:00
2022-06-30 11:26:40 -04:00
2022-05-19 09:42:17 +02:00
2021-09-29 11:56:13 +09:00
2022-02-15 11:13:49 +01:00
2022-05-19 09:42:17 +02:00
2022-03-28 16:47:48 +02:00
2022-05-19 09:42:17 +02:00
2022-05-19 09:42:17 +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.