1
0
mirror of https://github.com/postgres/postgres.git synced 2025-05-29 16:21:20 +03:00
Tom Lane 0f3637ace3 Make argument names of pg_get_object_address consistent, and fix docs.
pg_get_object_address and pg_identify_object_as_address are supposed
to be inverses, but they disagreed as to the names of the arguments
representing the textual form of an object address.  Moreover, the
documented argument names didn't agree with reality at all, either
for these functions or pg_identify_object.

In HEAD and v11, I think we can get away with renaming the input
arguments of pg_get_object_address to match the outputs of
pg_identify_object_as_address.  In theory that might break queries
using named-argument notation to call pg_get_object_address, but
it seems really unlikely that anybody is doing that, or that they'd
have much trouble adjusting if they were.  In older branches, we'll
just live with the lack of consistency.

Aside from fixing the documentation of these functions to match reality,
I couldn't resist the temptation to do some copy-editing.

Per complaint from Jean-Pierre Pelletier.  Back-patch to 9.5 where these
functions were introduced.  (Before v11, this is a documentation change
only.)

Discussion: https://postgr.es/m/CANGqjDnWH8wsTY_GzDUxbt4i=y-85SJreZin4Hm8uOqv1vzRQA@mail.gmail.com
2018-09-05 13:47:16 -04:00
..
2018-06-20 16:07:07 +02:00
2017-05-15 12:09:19 -04:00
2016-01-22 12:29:07 -05:00
2017-08-17 11:47:43 -04:00
2018-01-02 23:30:12 -05:00
2018-07-01 14:09:03 +02:00
2018-02-02 21:11:41 -05:00
2017-11-10 08:31:38 -05:00
2018-05-30 14:08:51 -04:00
2018-08-17 11:38:44 +12:00
2017-03-30 14:18:53 -04:00
2017-03-30 14:18:53 -04:00
2015-08-31 14:07:17 +02:00
2017-03-30 14:18:53 -04:00
2017-03-30 17:13:44 -04:00
2017-03-30 14:18:53 -04:00
2017-06-17 19:03:12 -04:00
2017-04-06 22:09:11 -04:00
2017-03-03 15:03:03 -05:00
2016-10-31 07:33:00 +09:00
2018-07-18 16:18:27 +03:00
2017-08-15 14:47:03 -04:00
2017-04-12 15:41:41 -04:00
2017-02-13 11:06:11 -05:00
2017-03-23 14:16:45 -04:00

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

Linking within SGML 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

<link>
	use to supply text for the link, requires </link>
	http://www.oasis-open.org/docbook/documentation/reference/html/link.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


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
----------

o  If you want to supply text, use <link>, else <xref>
o  Do not use text with <ulink> so the URL appears in printed output
o  Specific nouns like GUC variables, SQL commands, and contrib modules
   usually have xreflabels