Files
postgresql/doc/src/sgml
Tom Lane 18555b1323 Establish conventions about global object names used in regression tests.
To ensure that "make installcheck" can be used safely against an existing
installation, we need to be careful about what global object names
(database, role, and tablespace names) we use; otherwise we might
accidentally clobber important objects.  There's been a weak consensus that
test databases should have names including "regression", and that test role
names should start with "regress_", but we didn't have any particular rule
about tablespace names; and neither of the other rules was followed with
any consistency either.

This commit moves us a long way towards having a hard-and-fast rule that
regression test databases must have names including "regression", and that
test role and tablespace names must start with "regress_".  It's not
completely there because I did not touch some test cases in rolenames.sql
that test creation of special role names like "session_user".  That will
require some rethinking of exactly what we want to test, whereas the intent
of this patch is just to hit all the cases in which the needed renamings
are cosmetic.

There is no enforcement mechanism in this patch either, but if we don't
add one we can expect that the tests will soon be violating the convention
again.  Again, that's not such a cosmetic change and it will require
discussion.  (But I did use a quick-hack enforcement patch to find these
cases.)

Discussion: <16638.1468620817@sss.pgh.pa.us>
2016-07-17 18:42:43 -04:00
..
2014-05-06 21:28:58 -04:00
2016-07-08 10:06:45 +03:00
2016-07-14 22:28:58 -04:00
2016-04-01 16:42:24 +03:00
2016-05-04 14:07:00 -04:00
2016-07-12 13:30:48 -04:00
2016-01-22 12:29:07 -05:00
2016-05-31 13:56:25 -04:00
2015-04-26 10:33:14 -04:00
2016-07-08 09:26:53 -04:00
2016-05-11 15:01:44 -04:00
2016-01-02 13:33:40 -05:00
2016-01-02 13:33:40 -05:00
2016-05-31 13:56:25 -04:00
2015-11-25 16:31:55 +03:00
2016-06-03 16:08:45 +01:00
2015-08-31 14:07:17 +02:00
2014-05-06 21:28:58 -04:00
2016-05-31 13:56:25 -04:00
2016-04-01 12:21:48 +03:00
2016-05-03 21:06:25 -04:00
2016-03-23 23:01:35 -03:00
2016-05-26 11:58:22 -04:00
2016-07-14 22:28:58 -04:00
2016-05-31 13:56:25 -04:00
2015-06-03 20:19:47 -04:00
2016-04-29 13:03:58 -04:00
2016-04-08 16:56:27 -04:00
2016-05-01 21:37:43 -04:00
2016-04-01 21:53:10 -04:00
2014-08-30 10:52:36 -05: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