Thomas Munro 94ebf8117c Default to dynamic_shared_memory_type=sysv on Solaris.
POSIX shm_open() can sleep for a long time and fail spuriously because
of contention on an internal lock file on Solaris (and presumably
illumos).  Commit 389869af fixed the main problem with this, namely that
we could crash, but it's now clear that "posix" is not a good default.

Therefore, choose "sysv" at initdb time on Solaris and illumos.  Other
choices are still available by editing the postgresql.conf file.

Back-patch only to 15, because contention is much less likely further
back, and it doesn't seem like a good idea to change this in released
branches.  This should clear up the failures on build farm animal
margay.

Discussion: https://postgr.es/m/CA%2BhUKGKqKrCV5xKWfh9rnm%3Do%3DDwZLTLtnsj_XpUi9g5%3DV%2B9oyg%40mail.gmail.com
2022-07-02 16:23:39 +12:00
..
2022-05-19 09:42:17 +02:00
2022-05-19 09:42:17 +02:00
2021-09-29 11:56:13 +09:00
2020-02-26 13:05:30 -08:00
2018-10-11 11:43:56 -07:00
2022-04-08 00:26:44 -07:00
2022-05-19 09:42:17 +02:00
2022-05-19 09:42:17 +02:00
2020-07-18 22:43:35 +09:00
2021-04-07 13:52:26 +02:00
2022-05-19 09:42:17 +02:00
2020-10-19 13:48:00 +02:00
2020-06-07 13:18:36 +02:00
2022-06-30 11:26:40 -04: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
2019-10-25 20:39:41 +02:00
2017-10-17 15:10:33 -04:00
2017-10-17 15:10:33 -04: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
2022-05-19 09:42:17 +02:00
2021-01-05 14:26:37 -05:00
2020-08-28 08:19:12 +02:00
2022-05-19 09:42:17 +02:00
2022-05-19 09:42:17 +02:00
2022-04-06 23:06:46 -07:00
2022-06-30 11:26:40 -04:00
2022-06-30 11:26:40 -04:00
2019-09-08 10:27:29 +02: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-04-08 13:43:37 +12:00
2022-05-19 09:42:17 +02:00
2022-05-19 09:42: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
	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.