1
0
mirror of https://github.com/postgres/postgres.git synced 2025-12-09 02:08:45 +03:00
Files
postgres/doc/src/sgml
Tom Lane 74da4c71d6 Doc: improve protocol spec for logical replication Type messages.
protocol.sgml documented the layout for Type messages, but completely
dropped the ball otherwise, failing to explain what they are, when
they are sent, or what they're good for.  While at it, do a little
copy-editing on the description of Relation messages.

In passing, adjust the comment for apply_handle_type() to make it
clearer that we choose not to do anything when receiving a Type
message, not that we think it has no use whatsoever.

Per question from Stefen Hillman.

Discussion: https://postgr.es/m/CAPgW8pMknK5pup6=T4a_UG=Cz80Rgp=KONqJmTdHfaZb0RvnFg@mail.gmail.com
2021-11-10 13:12:58 -05:00
..
2020-07-05 15:37:57 +02:00
2020-09-10 14:15:26 +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
2021-01-29 14:09:41 +13:00
2021-09-26 19:18:23 +09: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
2021-07-29 21:39:40 +02:00
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
2021-07-16 12:39:23 +02:00
2021-01-02 13:06:25 -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
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
2021-08-06 20:56:18 +02:00
2021-09-29 11:56:36 +09:00
2021-07-16 12:39:23 +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.