1
0
mirror of https://github.com/postgres/postgres.git synced 2025-11-24 00:23:06 +03:00
Files
postgres/doc/src/sgml
Tom Lane 0ab1a2e39b Remove dead encoding-conversion functions.
The code for conversions SQL_ASCII <-> MULE_INTERNAL and
SQL_ASCII <-> UTF8 was unreachable, because we long ago changed
the wrapper functions pg_do_encoding_conversion() et al so that
they have hard-wired behaviors for conversions involving SQL_ASCII.
(At least some of those fast paths date back to 2002, though it
looks like we may not have been totally consistent about this until
later.)  Given the lack of complaints, nobody is dissatisfied with
this state of affairs.  Hence, let's just remove the unreachable code.

Also, change CREATE CONVERSION so that it rejects attempts to
define such conversions.  Since we consider that SQL_ASCII represents
lack of knowledge about the encoding in use, such a conversion would
be semantically dubious even if it were reachable.

Adjust a couple of regression test cases that had randomly decided
to rely on these conversion functions rather than any other ones.

Discussion: https://postgr.es/m/41163.1559156593@sss.pgh.pa.us
2019-07-05 14:17:27 -04:00
..
2018-07-16 10:48:05 +02:00
2019-06-13 10:03:56 -04:00
2019-07-05 08:34:54 +02:00
2019-07-05 08:34:54 +02:00
2019-07-05 08:34:54 +02:00
2018-10-11 11:43:56 -07:00
2018-06-20 16:01:18 +02:00
2019-06-12 23:05:40 -04:00
2018-06-20 16:06:03 +02:00
2019-06-09 11:25:56 +09:00
2019-07-01 12:50:55 -04:00
2019-07-05 08:34:54 +02:00
2019-04-08 22:32:46 +02:00
2018-07-16 10:48:05 +02:00
2019-04-03 17:40:29 -07:00
2018-07-16 10:48:05 +02:00
2018-10-03 12:48:37 -07:00
2019-07-05 08:34:54 +02:00
2019-01-02 12:44:25 -05:00
2019-01-02 12:44:25 -05:00
2019-03-29 08:26:33 +01:00
2018-07-16 10:48:05 +02:00
2018-08-28 21:33:32 +09:00
2019-03-13 13:41:14 +01:00
2019-04-08 22:32:46 +02:00
2018-08-14 22:54:52 +02:00
2019-05-09 09:16:59 +02:00
2019-04-03 17:40:29 -07:00
2019-03-29 13:36:24 +01:00
2019-07-01 12:50:55 -04:00
2019-07-01 12:50:55 -04:00
2019-02-17 20:23:10 +09:00
2019-06-09 11:25:56 +09:00
2019-07-05 08:34:54 +02:00
2019-05-26 18:28:18 +05:30
2019-03-27 23:10:23 +01:00
2019-03-27 23:10:23 +01:00
2019-03-30 08:15:57 +01:00
2018-08-28 21:42:45 +09:00
2018-07-16 10:48:05 +02:00
2019-07-05 08:34:54 +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

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

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